| | | |
|---|
Advanced search
Implement Blacklight advanced search on common fields | | | |
External repository harvest
Provide the option to harvest descriptive metadata (and possibly files) from external repositories into ScholarWorks, so they can be discovered in ScholarWorks as well. For metadata-only records, direct users back to the original record in the home repository. | | | |
Campus landing page
Implement new campus page to search campus records and browse campus collections. Add campus field to each collection and give campus managers ability to manage all campus collections. | | | |
Bulk upload
Allow for multiple items to be added to ScholarWorks at one time, instead of uploading items individually. | | | |
Title and description formatting on Collections
Ensure basic formatting for title and description on collections as with works. | | | |
ORCID import by author
Based on customizations other Samvera institutions have developed, allow users to authenticate an OAuth institutional connection between their ScholarWorks account and ORCID with full read, write, and edit permissions. | | | |
ORCID bulk import
Allow authors and administrators to approve manual and automatic bilateral record sharing and updates between ORCID and ScholarWorks. | | | |
Usage stats enhancement / robust statistical reports Notch8
Allow library staff to create reports from the dashboard, with options to filter and sort by various fields (e.g., campus, department, type) and date ranges. Reports should also include usage counts by referring site and user’s geographic location and (ideally) institution type.
For the public, we want to show basic view & download counts for each work. Ideally, we would be able to import historical usage stats from DSpace into Hyrax. | | | |
Save submission as draft
This enhancement would make it so that you can start an item deposit and save it while it is “in process.” The current set up does not allow for saving draft versions. | | | |
Top-level facet for model
e.g., student works, publications, dataset, educational resources, or whatever models we create. | | | |
Share-your-paper integration
Develop an integration that would allow faculty and students to deposit their research into ScholarWorks using Share-Your-Paper, an open source tool that makes it easier to get articles deposited into repositories. It’s currently free to individuals to use, and looking for institutional partners. | | | |
OJS > Samvera integration
Develop a crosswalk/harvesting tool that will export items from OJS into ScholarWorks for long-term preservation and additional access. There is interest from others in the Samvera community, so there could be options to break this fairly large project into smaller pieces for multiple organizations to work on. | | | |
Collection search
Include all fields in search and allow faceted search within collections. | | | |
Email alert enhancements
Allow campuses to enable email notifications for unmediated workflows, and allow depositors to choose to have others (i.e., faculty advisors or co-authors) cc'd on any email notifications. | | | |
Completed | | | |
Upgrade to Hyrax 2.9
Includes security and bug fixes, IIIF improvements. | | | |
ORCID links
Include in all forms the ability to add ORCID identifiers for persons in all roles (author, contributor, committee member, etc.). Add link to ORCID profile in the work record display. | | | |
Bulk metadata editing
Export all metadata or edit multiple metadata records at once using Excel. | | | |
SWORD service Notch8
Several CSU campuses use third-party ETD management systems – including Proquest ETD Administrator and a home-grown system at Northridge – to manage the thesis and dissertation lifecycle. The final step in that lifecycle is the automated deposit of the thesis into ScholarWorks. These third-party thesis management systems all support SWORD, a lightweight protocol that allows external systems to deposit content into an institutional repository. The CSU needs a firm to build a SWORD service into Hyrax to support both these thesis management systems and other potential third-party systems that would utilize SWORD. | | | |
Campus-limited view Notch8
We are currently implementing a shared Hyrax instance where library staff and end-users from multiple CSU campuses will be working in the same instance. When users authenticate, they will be assigned to a group that represents their campus (e.g., ‘sandiego’, ‘fullerton’, ‘longbeach’, etc.). Currently, Hyrax allows users to set ‘private’, ‘public’, or ‘institution’ view access to items. The ‘institution’ view allows any authenticated user to view the item, so in our case, CSU user regardless of which campus they are at. The CSU needs a firm to add a fourth option, to allow only users from a particular campus to view the item – that is, only users from the same campus group as the user who uploaded the item. | | | |
Long-term preservation using Glacier Notch8
With the current DSpace system, the CSU has a custom-built process that pushes an archival copy of each submitted item to an EC2 / Glacier bucket for long-term preservation. There is also a custom-built process to retrieve the item from Glacier, should the CSU need to. The CSU needs a firm to put in place a similar long-term preservation and retrieval process for items submitted to Hyrax. | | | |
Handle service integration Notch8
One of the key features of any institutional repository is a persistent identifier for each item. The CSU used the Handle service in the past with DSpace for this purpose, and campuses have come to rely on it. We will need a firm to both (a) resolve existing handles to their new location in Hyrax using identifiers that are being migrated to the new system along with other metadata for each item from DSpace, and (b) mint new handles for new items that are submitted to Hyrax. | | | |
Speed-up migrations Notch8
By far the most time-consuming part of the project is migration of existing data and files from DSpace into Fedora. Based on the Current estimates, we are projecting 12 months for this part of the project. The CSU needs a firm to provide a review of our existing process and provide recommendations on ways to speed it up, if possible. Additionally, we need a firm to provide recommendations around the potential implementation of Valkyrie. | | | |