ScholarWorks Update - January 2020
Here is the latest from the ScholarWorks project.
Vendor
The Chancellor’s Office is putting the final touches on a contract with the San Diego-based firm Notch8 to complete a number of development projects and provide second-tier support for ScholarWorks. We’ll be adding timelines for these development projects as those become available.
Data migration & controlled vocabularies
After a thorough metadata cleanup (thanks to all who were involved), we have kicked off San Francisco’s data migration to production this month. We also met with Channel Islands to review pre-migration data clean-up. Maritime and Fresno are in queue, and we’ll be working with those repository managers in the upcoming month.
With several campuses engaging in extensive data remediation work, we have gotten a bit behind our original timeline. We’ve updated the migration schedule accordingly, and will be incorporating data remediation work earlier in the migration process for upcoming campuses.
We’ve also recently reorganized our campus-based controlled vocabularies. Campus project managers may edit those, and we will update them in production.
Metadata & feature enhancement requests
Campuses may submit new feature requests or the new ScholarWorks and track those here.
They can also post metadata change requests and track the status here.
Digital Repository Committee
The DRC has hit the new year running. After some initial organizational meetings in December, the steering committee kicked off January by discussing accessibility remediation, DOIs, and a proposal for ORCID adoption. Meeting notes are open to anyone who is interested.
Metadata Working Group
The Metadata Working Group requests your help in getting a handle (pun intended) on the proliferation of identifiers currently in use across campuses by filling out our identifiers survey by February 7.
The survey seeks to determine which resource and author identifiers you would like to see in Hyrax, and what identity services might be worth integrating in future Hyrax development projects. Please share this survey with all relevant personnel at your campus, as we would like to obtain as much feedback as possible.
Additionally, the MWG is interested in how campuses are providing subject access. Please fill out our subject access survey by February 19.
That survey seeks to determine what type of subject access (whether controlled vocabularies, uncontrolled keywords, or something else) campuses are using as well as who performs this work (library staff? students? faculty?).
Digital Archives Working Group
The DAWG has created the Campus Repository Personnel Registry. Its objective is to identify personnel that have some responsibility for various areas involved in the creation and maintenance of the Institutional Repository and Digital Archives/Collections.
The registry is in the form of a spreadsheet with a separate tab for IRs and Digital Collections. Instructions are embedded in cells to define what is specifically meant by the various personnel we seek. Currently, we are locating the last remaining initial points of contact for each campus to facilitate the completion of the personnel registry. A call to all points of contact will go out in the next week or two to begin the process. We welcome any comments.
One-on-one meetings & documentation
We’ve set-up one-on-one meetings throughout February with all of the campuses involved in the ScholarWorks project. Like the last time we did one-on-one meetings in August and September, we will be checking in on campus’ forays into using the new system. We’ll also be walking through the steps for data remediation, both pre- and post-migration.
We’ve updated some of our training and documentation materials for ScholarWorks, including instructions on setting up campus workflows.