Imeji Standard Metadata Profiles

 Outdated

Use Case
Possible walk through for profile generation:
 * 1) The user creates a collection
 * 2) The user wants to create a metadata profile, therefore he can:
 * 3) Create an own metadata profile
 * 4) Use an existing profile as template
 * 5) Use a standard profile as template
 * 6) The user decides to use a standard profile: The metadata profile editor is populated with the standard metadata statements

Backend Specification

 * An administrator can upload standard profiles from the admin interface
 * Question: Can we manage those profiles in CoNE? Therefore they could be reused by other instances
 * xsd import is already realized for the import tool. To check what we can reuse.
 * The profile will be stored as a template for a collection. This means there is always a 1:1 connection between profiles and collections
 * The profile will be stored in native imeji format
 * In the background a standard mapper element will be created for the relation to the standard profile
 * The user can edit a standard profile

Frontend Specification

 * Standard profiles are provided for selection (create metadata profile page) in a separate drop down or in an options drop down with other templates
 * When the user edits a standard profile it should be clear for him that he leaves the standard (plus standard export)
 * In the view page of metadata (image page), it should be possible to view the namespaces for standard profile (perhaps in a new tab)

Supported Metadata Standards
Which metadata standards should we support, please enhance the list. If possible link to the RDF representation of a standard:


 * VRA
 * MODS
 * DC Terms

Metadata Export
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 standards (as defined before) should be all supported by the export. Since the mechanisms 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)


 * METS/MODS for DFG-Viewer (as required by the DFG)