Date

02 Nov 2017

Elements Repository Connector- Meeting Notes

Notes taken by Rachel Appel (Unlicensed) on 7/2/17, reproduced verbatim by Gabe Galson in confluence on 6/25/2018

...

Kelsey Rosell: VP of Institutional Sales for Digital Science

Kate Byrne: Repository Platforms Product Manager

Ulisse Gallo: Account Manager

----------------

Annie Johnson

Rachel Appel

Delphine Khanna

David Lacy

Emily Toner

Cynthia Schwarz

Demo

Can provide local information/instruction
Can select embargo period and make comment
Suggest re-use license (with guidance)
Creates datasource icon for record and information about deposit
Repository is treated as datasource for Elements, anything can be harvested back into Elements
Creates DSpace ID that maintains link between Elements and repo
Sends metadata to DSpace

Can be sent to live or can be put into review queue
Can modify metadata and create custom map file between Elements and repo
Edit metadata record in DSpace and syncs with Elements version (batch modifications run in the background but needs to run through entire harvest for non public records. The public ones are harvested through OAI PMH to identify modified records)
Dspace 6.1 has embargo support (not the previous version)
Connect via API URL, username, and password

Also takes OAI pmh baseline URL (to enable differential harvest) and SWORD endpoint

Connector by default is in both directions
Develop harvest crosswalks, turn it on, pulls in copy to map to corresponding record in Elements
Depositing from Elements: immediately harvested back via ID designation
Metadata edits can only be pushed from repository (working on the reverse)

Can work with hosted or local DSpace; no customers working with DSpace Direct yet (as far as she knows)
TIND: had early conversations, but no clients
Does usability studies when a client is interested and the framework is extensible
Different versions of DSpace vs what is and what is not supported
Website has tools and information
Has RD2 sandbox in Elements Preview instance
Open Access Module:

Repository tools module + open access tool
Can select publication types for OA with data specification
Can work with multiple integrated repositories
Can be used without OA policy, can be used as a framework (invisible)
Configure compliance settings: deposit deadline, embargo maximums, compliant file versions
Can filter by groups in Elements
Dashboard to monitor what is being deposited/not yet deposited, you can deposit on people behalf, send emails to the faculty (reminders, etc)
Pubmed central: get directly links to the full text (OA)

You still need to “click the button” to deposit each file. But they are very interested in exploring options for automated.

Track dates for depositing and deposit rates
Keep track of “user engagement” (who has not uploaded anything in a long time? Who has items waiting for deposit?)
You can generate a number of reports (OA Reports)
Action prompts for publications that fall into the OA policy
Claim+ to claim and then take through link to funding and then deposit
OA dashboard: high level with summary/portion of publications deposited
Implementation:

Decide how you want to use the system (workflow, metadata structure, policies, etc.)

Set up process: subscribe to ongoing license, one-time implementation fee (relatively low), upgrade to “enterprise” from “faculty reporting” solution
Enterprise: adds repo and OA monitor modules + impact (but we already have impact because they gave it to us for free).

About $20,000 extra annually (+ 1 time fee) - Although some discount will apply (e.g., because we are a “reference client”)
Kelsey will send us the details.
They can also prorate it between now and February (which is the time for our license renewal.
If we were to a Figshare customer we would also get another extra discount (because we would get a multi product license)
URL to sandbox

Browser not supported