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)
- 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, checkboxes etc. which can be distracting).
Supported Metadata Standards[edit]
Which metadata standards should we support, please enhance the list. If possible link to the rdf representation of a standard:
- VRA
- MODS
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:
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.