Difference between revisions of "Imeji Standard Metadata Profiles"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) |
Kleinfercher (talk | contribs) m (→Use Case) |
||
| Line 7: | Line 7: | ||
# The user creates a collection | # The user creates a collection | ||
# The user wants to create a metadata profile, therefore he can: | # 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 | # The user decides to use a standard profile: The metadata profile editor is populated with the standard metadata statements | ||
Revision as of 07:21, 22 April 2013
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.)