Difference between revisions of "Talk:Checklist for Metadata Changes"
Jump to navigation
Jump to search
| Line 33: | Line 33: | ||
*content-categories are not complete in VES on Colab | *content-categories are not complete in VES on Colab | ||
**check different values in the data and synchronize with VES | **check different values in the data and synchronize with VES | ||
*visibility in file-profile: add restricted | |||
*check different values in the data and synchronize with VES if needed for all metadata where VES are used | |||
Revision as of 13:07, 26 November 2009
- Core service
- 1.1.3 will be used to avoid dependencies from other solutions
- 1.2 requires new releases of Faces and VIRR !!!
- independent tasks
- dependencies
- vacations
- Julia:
- tests
- SVM
- Lars
- date - release on live
- possible to check: 21-23.12
- otherwise ende January
- lars
- not needed
- downtime
- 1-3 days (to be checked)
- identifiers
- resolved will not be changed at all
- escidocadmin
- robert- organizational units
Metadata decisions[edit]
- Vocabulary encoding schemes
- used URIs as values in metadata
- used URIs may be mixed from different external VES
- synchronize the actual enum- values in current schema with missing URI values in eSciDoc VES
- synchonize the new URI values in eSciDoc VES with the schema
- all enums have to have URIs as values instead of strings
- check if changes are only necessary in JibX
- content-categories are not complete in VES on Colab
- check different values in the data and synchronize with VES
- visibility in file-profile: add restricted
- check different values in the data and synchronize with VES if needed for all metadata where VES are used