Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
rdms:metadata:metadatatemplates [2023/09/12 14:32] – [Examples of Template Usage] giulio | rdms:metadata:metadatatemplates [2023/09/13 09:11] (current) – WebApp to web portal (consistency) jelte | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Metadata Templates ====== | ====== Metadata Templates ====== | ||
- | As described in the previous sections, every user of the RDMS can easily add metadata to their objects and collections either via the [[rdms: | + | As described in the previous sections, every user of the RDMS can easily add metadata to their objects and collections either via the [[rdms: |
As the name suggests, metadata templates are pre-configured metadata entry forms that the user can define in order to have **a consistent way of recording metadata** for a given data object or collection. For example, you could have a template attached to a collection recording the "Name of the PI", " | As the name suggests, metadata templates are pre-configured metadata entry forms that the user can define in order to have **a consistent way of recording metadata** for a given data object or collection. For example, you could have a template attached to a collection recording the "Name of the PI", " | ||
The advantage of a template over manual entry of metadata is that the user has a pre-defined list of entries. This reduces the risk of forgetting to record a given value or to have objects with different metadata entries, even though they should have been matching. | The advantage of a template over manual entry of metadata is that the user has a pre-defined list of entries. This reduces the risk of forgetting to record a given value or to have objects with different metadata entries, even though they should have been matching. | ||
Line 164: | Line 164: | ||
++++ | ++++ | ||
- | For the use of '' | + | For the use of user-defined types in the creation of a template, we want to create a metadata entry that records what instrument was used to record a certain set of data. We also want to record the instrument settings and put restrictions on certain fields. We also want to make sure that certain metadata entries are always recorded when this specific template is used. |
++++ Click to display example | | ++++ Click to display example | | ||
- | Entries: | + | First we need to create a user-defined type to select our instrument from. Figure 11 shows how to create a '' |
- | * Instrument name | + | |
- | * Settings | + | {{ :rdms: |
- | * Conditions | + | |
+ | < | ||
+ | < | ||
+ | Figure 11 | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | Next, we need to create our template. Figure 12 shows how to do so, while using our own type for the choice of instrument. Please also notice that we restrict the input of all our variables to just one entry, except for the '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | < | ||
+ | < | ||
+ | Figure 12 | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | Finally, we can once again navigate to the object we wish to attach metadata to and right-click it. Select '' | ||
+ | |||
+ | **Note**: | ||
+ | The web portal will display one value more than the minimum for non-mandatory entries. In our case, '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | < | ||
+ | < | ||
+ | Figure 13 | ||
+ | < | ||
+ | </ | ||
++++ | ++++ |