2018-09-7 Meeting notes- Cornell IR Call
- Gabe Galson
Owned by Gabe Galson
Sept 14, 2018
4 min read
Loading data...
Link to original google doc
Discussion items
| Question | Answer |
|---|---|
| When was repository launched? What was the impetus for starting it? | 2005. Started in partnership with library, which has taken over from faculty as the driving force behind it. No open access policy at Cornell. ETD hosting is an important function. The scope of ETD collection is constantly expanding. |
| How did you decide on the organization of the repository? | Communities [schools and colleges, centers and institutes, honors theses are all separate communities] and collections. They're not as well organized as the cornell folks would like. Were they to start over they would be more deliberate/thoughtful about this org structure. Browse page is slow to load bc of the complexity; DSpace issues: Slow loading... DSpace has an unacnowledged problem with this. Raises questions about DSpace's scalability; they're quite large but not as large as some. DSpace's checksum reporting doesn't work in their repository... other DSpace users have reported the same problem. They're on 6.2. There's a bug fix on 6.3... Buggy/slow: https://ecommons.cornell.edu/community-list |
| (follow up) Current communities include schools/colleges, centers/institutes, and honors theses? | |
| How did you decide on intellectual scope? Why include admin reports, meeting agendas, etc? | Gail: We have a loose collecting policy. Jim's collection's scope (ECommons): --Also collects materials of interest to the schollarly community (this comprises 80% of the content). For example, archival material, labor relations material, CVs, etc. This material doesn't have to be published by the uni, and it doesn't have to be archival. |
| How is work handled? How many people are involved? | -Batch upload is the main method by which content is ingested, meaning a staffer must be involved. Survey of repositories: There are over 3 structurally and administratively distinct Cornell IRs. ECommons: -No self archiving -The process is librarian-mediated from top to bottom Jim's repositories: -Serves 200-ish faculty members -Staffing levels [missed this, ask annie] -Gail and her staff's time commitment: 30% of her job. 30% of another position (metadata, workflow). 30% of an IT person's time. 20% of another user support position. |
| How do you populate the repository? (Harvesting, submissions, etc) / How much manual work/mediation is needed? | See above Aside: They're not using any sort of RIM system (ie symplectic). |
| Who can contribute works to the IR? We are considering alumni, is this something Cornell does? | -Alumni, non-Cornell academics(with sponsor at institution) are both permitted. -Faculty, Grad Students and Staff have a mechanism for requesting whatever they want -Undergradute senior honors theses too, although they're working through a mechanism for verifying that honors theses submitted are legitimate. **FERPA statement added to license to accomidate this. Gail utilizes DSpace's license bundle for this purpose. Scanned FERPA agreement forms can be manually inserted into the DSpace license bundle. -Labor Scholars worldwide (Cornell's IR is the premier collection of this sort of material) |
| How is the repository working for data sets? | They currently accept data sets. Data friendliness wishlist compiled a few years ago... mostly complete at this point. Items: -DOI generation -Versioning (DSpace does this now) -Issue: when a paper and dataset are submitted as a single dspace item, how is this classified? For this and related reasons Gail avoids organizing IRs by material type. University of Minnesota runs their data and research repositories out of the same DSpace instance, using two separate metadata schemas. |
| Do you have an open access mandate? | No. |
| What are your goals for the repository in the coming years? | -Implement service mgmt practices (joint effort with IT). -Staying current with the DSpace version (a significant task) -Metadata cleanup project -Better statistics (currently adequate, could be better) -Looking at Samvera, however DSpace is currently meeting their needs and Samvera's still half-baked -Become more active DSpace users, contribute so as to gain clout/influence future dev, and be a good citizen. |
| What about rights? | |
| Do you think that the IR has been successfully adopted by faculty and the campus community? | -ECommons is relatively unknown. Faculty survey indicated a desire for an IR without a knowledge of Cornell's current IR. -Jim's repository has been adopted by almost 80% of the 200-ish faculty members |
| What can you tell us about usage? | |
| Do you do any kind of advocacy? | |
| What is your retention policy? | http://guides.library.cornell.edu/ecommons |
| What formats do you accept? | http://guides.library.cornell.edu/ecommons |
| Do you have all your policies written down? | http://guides.library.cornell.edu/ecommons |
| Generally speaking what are your copyright policies? What do you not allow into your IR? How do you enforce these policies? | Prospective licensing... rather than requiring it to be approved upon each upload, they've figured out a way legally/administratively to cover entire units and schools. Gail: -We don't screen incoming content -We rely on self policing from submitters- people could be depositing stuff they shouldn't be, the IR managers will take it down if they recieve a take down notice but otherwise won't call it out. They rely largely on SHERPA RoMEO for guidance. They've basically turned down a book. Jim: Stays vigilant, but the situation is similar |
| Which departments are using the IRs; Are open formats required? | Open Formats not required, but are encouraged. -Engineering, Ag and Life Sciences are most enthusiastic contributors. |
| Dublin Core Schema | -They've modified their DC schema -'Related' Field used to link datasets and papers -Items can be deposited (then withdrawn) just to create a handle (in case of embargo). (Many journals require a persistant ID to submit and this workflow accomidates the period before an article is accepted). Or, a metadata only-item (with dummy file) can be uploaded. |
| Participants: | Gail Steinhart, Jim DelRosso, Wendy Kozlowski Everyone's happy to field questions after the session Gail manages main dspace- ecommons Jim manages two school specific digital commons repos (school of hotel mgmt, ILR industrial labor relations) |