Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: correcting/cleaning up some of my own statements from last time

...

  • positive feedback from March 20th mtg - phase 1 deemed "cheap" by a few of the committers
  • 2nd person who expressed interest: Yanan Zhao from The University of Auckland - Val to circle back with Yanan
  • what are the next steps?
    • more refining work to do
    • very technical and complex
    • should send targeted emails: invite people personally to give input, all sponsors?
      • ask for: need input, could you tell us what you need
    • breakdown discussion into smaller (provocative?)
      • are you actively using automated ingest or export API or OAI - they will be affected by metadata improvement project 
    • who should we target? create an institutional profile
    • what are we going to do for lockdown - this is what is planned - this is why, vote, give feedback, join the gang 
    • identify what functions will be impacted 
    • Monica agrees with approach, hoping to have Rice Univ DSpace developers help
  • Bram's ?s on lockdown:
    • 4.x dspace date schema - system genarated by dspace, you can edit it manually,
    • dspace schema is meant for fields that are reuqired required to function - dspace specific, admiinistrative  administrative field to do somehitng something in dspace, not appropriate to use dublin core for dspace
    • pull out dspace schema in 4.x is all that's been decided, not sure what comes next in 5.x
    • moving the updated SWORD fields into an admin space - part of 4.x
    • dspace specific and SWORD specific shoudl be kept out of system admin? -
    • last modify date - what is item metadata admin vs. not
    • when you have the same terms we would want to have provenance for the item dc terms provenance and dspace terms provenance - maybe we have a "date availble" in both or is it different depending on the item
    • check sum generated is really only in dc provenance for an item metadata After investigating this later on, it was clear that checksums are stored very well in the DSpace RDBMS model. See the database model for more information.
    • later phase of project: look at PREMIS to clean up provenance issues - metadata at bitstream level, not just item level

...