Page Comparison

Date

23 28 Oct 2019

Participants

• Rachel Appel (Unlicensed)

• Gabe Galson

• Annie Johnson (Unlicensed)

• Noa Kaumeheiwa

• Alicia Pucci

• Fred Rowland (Unlicensed)

• Gretchen Sneff (Unlicensed)

• Emily Toner

Notes

1. Update on soft launch progress

   1. Procurement process

      1. Atmire (our vendor) has been approved! We will be in conversation with them about next steps to get the platform (Open Repository) up and running

   2. DataCite

      1. Our membership was approved and we can start minting DOIs (but not during the soft launch)

   3. Beta tester groups + workflowsworkflow

   4. DataCite

   5. Procurement process

2. TUScholarShare questions/ issues

   1. What do we do with works that fall within more than one community? (e.g. Felix Udoeyo’s textbook published by North Broad Press)

      1. Right now Communities are based on affiliation/ format/ use; Consider what community works best to enhance the discoverability of the work

      2. Can test co-locating records that fall within multiple collections - this can be done in our instance to allow one to locate records within multiple collections

      3. We don’t want to police where works belong, but should we consider asking the depositor?

      4. Ex: Steven Bell’s works are within the ‘Produced at Temple’ community, but shouldn’t they belong in the ‘Faculty/ Researcher Works’ community? Do these cross communities? Should they all be displayed together?

   2. Creating sub-collections for departments/ centers/ organizations - should we do this only if it’s specifically requested?

3. Review Research Datasets Dataset policy

Next Steps

• Consider which facets would be most useful to users when filtering works in TUScholarShare - this is something that needs to be brought to Atmire to be implemented; this would answer the two issues addressed above

• Gretchen Sneff (Unlicensed) and Fred Rowland (Unlicensed) will make revisions to the Research Dataset Policy

• Alicia Pucci will add the revised version of the Research Dataset policy to the main policies document

  • Standardize language of the main policies document regarding use of terms like ‘users’, ‘depositors,’ ‘submitters’ etc.

  • This will be shared with the group + we will determine where/ how this should be presented

• Test co-locating works that span multiple collections in TUScholarShare