Versions Compared

Old Version 5

changes.mady.by.user Sarah Potvin

Saved on

compared with

New Version Current

changes.mady.by.user Sarah Potvin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Some ideas mentioned previously were:

  • crosswalk: DC experts to help create a crosswalkreview and validate the mappings developed by the metadata subgroup
    • You mean from the old schema to the new one? Are you sure a crosswalk is needed? An SQL script might be needed instead. In any case, the first step will be to finalize the mapping of fields from old to new (a table should be enough); will this be purely a mapping or are any transformations of field values also necessary?
    • I think we're looking at mappings at this stage.
  • admin schema: identify which metadata should move to the admin schema
    • dc.date.accessioned
    • dc.description.provenance
    • dc.source (question)
    • dc.source.uri (question)
  • impact: identify all the areas in DSpace that will be affected by changes - input forms, item pages, browse pages, etc.
  • user interface: identify and get agreement on tasks that should have a new UI screen, help design and develop UI screens
  • tool development/refinement: review and provide feedback on "MetadataMapper" by Richard Rodgers, identify other tools that need to be developed for phase 1 implementation
    • where can we find the tool
  • other ideas????

...