2018-06-22 Meeting notes

Owned by Gabe Galson
Last updated: Sept 18, 2018
2 min read

Date

Attendees

Goals

  • Gain an understanding of Elements' Repository Tools 2 features, in particular the Repository Connector that will allow us to link DSpace and Elements 
  • Learn what's involved in bridging the gap between Elements and DSpace; Access documentation defining this process 

Notes

--Cynthia's overview of our interest in the Connector: Primary driver of project at TU is connection with Elements.  Eventually we’ll use it for electronic theses and dissertations.  Eventually, perhaps, Dspace will store data sets. Eventually, perhaps, out of print pubs can be deposited into DSpace (through elements? Through dspace?).  We want to make faculty’s work more openly accessible. Currently our OA policy is voluntary.

--Elements folks: Main work would be metadata and field crosswalking.  Elements or Temple could configuring integration.   Our integration should be (relatively) simple since we can design our DSpace to mimic our Elements installation's structure

--It's a two way crosswalk: “Harvest” (DSpace->Elements)vs “Deposit” (Elements->DSpace)

--Researchers must click 'upload to dspace' on each article they wish to "Deposit".  This function is comprehensive, but is somewhat buried in the interface.  Rosalind anticipates poor faculty participation when it comes to this step; Cynthia expects this to be a librarian-mediated function.  

  • New feature: Researchers can add additional files after initial deposit (but cannot delete).  
  • Feature:  ‘Use object neighborhood’ feature allows info Elements pulls from the wider web to be added to the DSpace record
  • Feature:  Creative Commons licenses can be auto-applied
  • Note:  Metadata alone cannot be deposited to dspace, a file must accompany it.  Cynthia says we have no interest in adding file-less metadata to the DSpace, so NBD.   

--To prep DSpace for connection, OAI, Rest, & SWORD must all be enabled.  Jim turned on OAI, is confirming that he turned on Rest.  Gabe will look into turning on SWORD (which can also be used, hypothetically, for ProQuest ETD ingests).  

--Gabe's Q's:

  • What happens when we upload ETDs to the DSpace, they're harvested into Elements, and no corresponding faculty profile exists? 
    • Kate's A: they are retained by the system, become 'orphans', and are associated with an appropriate researcher profile once one is created.
  • Deposited files can go directly into the repo, or into an approval queue, correct?  How is this configured?
    • A: Per-collection, on the DSpace side.  
  • Can the deposit process be automated?  
    • A: Not currently

Action items

  • Enable SWORD
  • Enable DSpace API
  • Examine fields currently used in Elements, devise rough road map to address metadata issues earlier rather than later
  • Test Connector using Elements dev installation