Imeji Standard Metadata Profiles
Use Case[edit]
A metadata profile editor does not want to create an own metadata profile but he wants to integrate a standardised metadata set.
Possible walk through:
- The user creates a collection
- The user wants to create a metadata profile, therefore he can:
- Create an own metadata profile
- Use an existing profile as template
- Use a standard profile
- The user decides to use a standard profile: The metadata profile editor is populated with the standard metadata statements
Open questions:
- May the user be allowed to change the standard metadata profile (delete statements, change cardinality etc.)?
- Would be a problem if we support standardized exports (especially with transformations)
- Idea: The standard metadata profiles stays untouched but the user may create derivatives from them (children that inherit all statements from the standard metadata profiles). These derivatives are copies that are saved under another name but are fully editable. That way the standard metadata profiles and their standardized exports are always available. To support export for the derivatives the mappings should work in a similar fashion, that is the user may create derivatives of the standard mappings in order to retain the used standard statements while also be able to add or delete statements in an easy way. Standard mappings shall be documented to let the editor identify each statement at a glance. --Jroeder 13:19, 22 April 2013 (CEST)
- I agree with Jörg. We have 2 object:s the profile and the mapping. When using a template, the user gets both predefined, but can modify them. The original standard template is not affected by the changes. But we could think a way to create new templates and/or to share profiles and mappings between collections.--Bastien 16:56, 30 April 2013 (CEST)
- GUI issue: How can we best display such profiles (it is possible that we have a deep hierarchy, long profiles etc.)
- Probably a start to optimize profile layout? As it gets very overloaded when one has many metadata statements. Talk:Imeji_Standard_Metadata_Profiles
- Idea: When editing a profile the statements are displayed as a text list, the statement can be unfolded if I want to edit this specific one. (Therefore we do not have as many buttons, check boxes etc. which can be distracting).
- See also Git:Improve metadata profile editing, Git:Metadata fields parent-child hierarchy,
Supported Metadata Standards[edit]
Which metadata standards should we support, please enhance the list. If possible link to the RDF representation of a standard:
Metadata Export[edit]
As we now provide standard metadata we can also provide standardized exports (via various transformations which are already available). Please add the export formats you want to have supported (if possible plus xslt from format of standard list above to export format):
- the metadata standarts (as defined before) should be all supported by the export. Since the mechanismus should be generic (up to the XSLT file which might be defined for each format), this should not be a major effort. --Bastien 17:01, 30 April 2013 (CEST)
Enhancements[edit]
- It would be nice if the admin could add predefined metadata profiles. Therefore he could also integrate native metadata or add other profiles as needed. (integrate into admin area?)