2018-09-14 Meeting notes- UMinn Repository Call
- Gabe Galson
Owned by Gabe Galson
Sept 14, 2018
4 min read
Loading data...
Link to original Google Doc
Discussion items
| Question | Answer | Link1 | Link2 |
|---|---|---|---|
| When was the DRUM repository launched? What was the impetus for starting it? | -They decided to augment their original IR for data. At that point they had substantial DSpace experience, confident devs -DSpace 6.x at present. They created a custom design and homepage. Used DSpace themes, which trickle down to the item level in an automated way. | https://conservancy.umn.edu/handle/11299/166578 | https://conservancy.umn.edu/ |
| (Only if not included in above answer:) What other IRs do you support at UM, how does DRUM relate to them? | ...Several others | ||
| How did you decide on the organization of the repository? You don't seem to have the separate communities that most DSpace instances have? Is that consistent across the repositories? | -For the data repository there's a flat stucture (no communities or collections). Why? because it made it easier to brand it as one discrete thing, via the public facing UI. -They changed the configuration of their DSpace so that anon users in the uni community could log in and deposit to any one of four collections. out of the box Dspace requires explicit authorization for each and every user who'se to contribute. Upon loging in the user can choose which collection do you want to contribute to. So, in order enable this, they structured their IRs as described. | ||
| Follow up: Given DRUM's flat structure, how do you make content browsible by department? | They don't do this. In fact, they don't include department info in the metadata of DRUM items. | ||
| How did you make the decision to brand the data repository (DRUM) separately? | It's a product that's easier to sell the faculty community on if it serves a single function. -Because it fulfills so many needs, the IR's identity can be quite ambigious to faculty. The [percieved] tight focus of the DRUM repository lets people understand its purpose; it's usually refered to seperately from the IR that contains it, on the back end. | ||
| How did you decide on intellectual scope? Why include admin reports, meeting agendas, etc? | -Their IR is the traditional home of whatever would have gone to University Archives. The Uni archivist is directly involved in the IR project. - -Rules: at least author must be affiliated with the university. -Unanswered question: What is data? This is what they have on this so far: must be machine actionable | ||
| How is work handled? How many people are involved? How does that compare to the UM DC? | Staffing: DRUM- much more hands on than UDC, much more resource intensive; **What they do for it: determine if data contains any personally identifiable information **Obtain a participant aggrement from each and every contributor (1 pg form). However, this resulted in a majority of data submissions being rejected. -6 positions devoted to DRUM part time **In the past they had graduate students with appropriate subject specialities reviewing submissions -3 person team for Digital Conservances, 1 developer (20% of their time) UDC- self deposit driven; some digitization done for UDC deposit | ||
| How do you populate the repository? (Harvesting, submissions, etc) / How much manual work/mediation is needed? | See above | Data curration network: Not every institution can have a data curration staff. It's a platform for shared data currator work across 8 instutions. They're trying to grow responsibly, and are currently not accepting new member institutions | https://www.continuum.umn.edu/2018/04/launching-the-data-curation-network/\ |
| Do you use a RIM? Is it connected to the repository? | -They have an OA policy since 2015. -They do have a RIM (Experts- El Sevier version of Elements). However they've opted to not populate the IR via the RIM. They invested heavily in this system, however, they're not at the point where they can support the briding of the gap between the two systems or two projects. -Most of their datasets were deposited because they're associated with a journal article. Troubling, because they tend not to be full data sets, but rather the subsets of these that pertain to the article. | Only datasets in DRUM get a DOI/ indexed in DataCite | |
| Who can contribute works to the IR? We are considering alumni, is this something Minnesota does? | -One author must have a UMinn affiliation. -Alumni? they don't currently. Authentication would be an issue, since the login system described depends on having a current university ID | ||
| How is the DRUM repository working for data sets? Software? | |||
| Are there linkages between datasets and articles deposited and vis-a-versa? How do you handle that and how do you handle split deposits? | -They encourage the separation of the dataset and article, so they're individual citable objects. -They use the specialized dc.relation fields for this. ('based on', 'has part', etc.). | ||
| Do you have an open access mandate? Does that have specific implications for data, sw? | Yes, but they're not enforcing it in terms of the repository. No OA access data policy -No effect on the DRUM, as the OA policy only covers articles (not monographs or data) -They also have a reserach mgmt policy | ||
| What are your goals for the repository in the coming years? | -Where does the repository fit in? This is still being decided as their IRs develop. -Education, Policy, Advocacy... all areas for growth. -concrete goal: tie in Globis, handle big data. | AAPU- bringing ppl together in DC to talk about open data policies. | |
| What about rights? | |||
| Do you think that the IR has been successfully adopted by faculty and the campus community? | |||
| What can you tell us about usage? | |||
| Do you do any kind of advocacy? | |||
| What is your retention policy? | Content submission to the University Digital Conservancy is permanent. Under certain circumstances an item in the Digital Conservancy may be removed from view (e.g. due to a violation of University Digital Conservancy deposit agreement). In order to retain the historical record, upon an item's removal the following statement is displayed: "Item Withdrawn. The item you are trying to access has been withdrawn from the University Digital Conservancy. If you have any questions, please contact Digital Conservancy staff." | ||
| What formats do you accept? | |||
| Do you have all your policies written down? | https://conservancy.umn.edu/pages/drum/policies/ | ||
| Generally speaking what are your copyright policies? What do you not allow into your IR? How do you enforce these policies? | |||
| Which departments are using the IRs; Are open formats required? | |||
| Dublin Core Schema | |||
| Supporting documentation, policies | https://conservancy.umn.edu/handle/11299/171761 | ||
| Participants: | |||
| DRUM: | https://conservancy.umn.edu/handle/11299/166578 |