Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: adding clarifications

...

Sue: exploring learning object repos - does anyone know of any learning repos using  

 

2) ALA meet up Fri 1/28 eve: Sarah P., Amy - Sarah P. to send msg to see if anyone else is interested  

3) Update DC

Sarah P: clarify the the level of lock down

  • make additions (qualifiers to elements in the schema) but not allow deleting or modifying fields unless you go through 2 step process - set up in configuration file
    • Current default behaviour:
      • fields can be added, changed or deleted from any schema
    • Proposed default behaviour
      • qualifiers can still be added
      • entirely new fields can still be added
      • existing fields from a standardized schema can not be deleted
      • existing fields from a standardized schema can not be altered/abused for something non standard
    • Proposed "override" behaviour
      • Repository managers can override the new default behaviour by flipping a safety switch in the dspace.cfg
      • After flipping the safety switch, they can do changes and deletions to any field in the interface just like before.
  • need for robust upgrade/migration tools
  • Sarah to make refinements on proposal

Bram: How does DCAT proposal intergrate with other projects

  • "Metadata for All" - fully included in the proposal for metadata enhancement. So no need to ask about both of them in the DCAT proposal already
  • "Proposal for Metadata Enhancements" - technical description of changes, but seems consistent/aligned w/DCAT proposal
    • all DCAT members should review wiki page, make sure it is consistent with DCAT proposals, post questions in comment section at the bottom of the page
  • Amy to create wiki page for proposal: Proposal to Update QDC Registry and Add DCTERMS Registry
  • Gather JIRA tickets that might be affected by DCAT proposals - put on wiki page w/the proposal - metadata team and Bram

...