...
- Best practices of how to make metadata changes - where, how - to maximize interoperability and keep schemas compliant
- Techiniques/tricks of how to harvest and manage metadata
- Implications of proposed changes – how people should prepare their DSpace instance for what's coming
- Other ideas for education?
- Better documentation and education about how namespaces can be filled-- education that moves beyond defining schema/registries. Broad request!
2) Breakdown project / proposal phase work into chunks and solicit specific help from community - identify what type of help we need and some idea of when we need it – and assign/request volunteers for each chunk
- need DC expert to help with crosswalk
- need help determining what metadata, if anything, should be moved to the "admin schema." Possibility of attention to whether this admin metadata can align with PREMIS or other existing standards.
- need help determining what metadata should be moved to the "local schema." Request that we provide a standard namespace URI for this schema that DSpace defines as being meaningless beyond the schema.
- need help identifying and addressing the affected areas: input forms, item pages, browse pages
- need to develop/revise UI screens - agree what's included and create UI screens for other tasks, make adding new schemas easier, etc. Also request for better documentation of process of adding schemas.
- need to develop tools/documentation/references/resources to help people with the transition - maybe a tool that would show how making a migration change in metadata might affect other operations like indexes, crosswalks, etc.
- Other?
- possibly outside of scope, but request for including standard ETD-MS namespace
...