| Info |
|---|
Submit enhancement requests here. Follow progress on Trello. |
Enhancement | Status | Priority | Updated |
|---|
SWORD service 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.About us page
With links to deposit agreement (really the visibility meaning) and other information, linked in header | |
YellowTESTING20210301Author fieldMake author a composite of multiple fields – name, email, ORCID, and institution – and preserve author order as entered02 |
Usage stats (works)
Track and show historical view & download counts for each work. | |
YellowTESTING1b20210301Bulk upload / editing / export
Allow for multiple items to be added to ScholarWorks at one time, instead of uploading items individually. Also have ability to export all metadata or edit multiple metadata records at once using Excel. Also, for the campuses whose main repository is not ScholarWorks (e.g., bepress, Islandora, Esploro), provide the option to harvest descriptive metadata from their repository into ScholarWorks, so they can be discovered in ScholarWorks as well. These metadata-only records will direct users back to the original record in the home repository. | | Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
| 2 | 2021-03-01 |
ORCID integrationBased 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. Allow authors and administrators to approve manual and automatic bilateral record sharing and updates between ORCID and ScholarWorks. 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 and ensure that author lateral links in ScholarWorks return only results limited to that ORCID identifier, when available.02 |
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. | | Status |
|---|
| colour | Blue |
|---|
| title | DEVELOPMENT |
|---|
|
| 3 | 2023-06-01 |
Usage stats (campus)
Top ten downloads and perhaps geolocation of stats for campus landing page. | |
development320201209 enhancement / robust statistical reports(staff)
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 | | Status |
|---|
| colour | Blue |
|---|
| title | DEVELOPMENT |
|---|
|
| 5 | 2023-11-02 |
ORCID bulk import
Allow authors and administrators to approve manual and automatic bilateral record sharing and updates between ORCID and ScholarWorks. | | Status |
|---|
| colour | Blue |
|---|
| title | DEVELOPMENT |
|---|
|
| 6 | 2023-06-01 |
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. | | Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
|
4 | 2021-03-01 | 7 | |
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. |
5| Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
| 8 | |
Top-level facet for model
e.g., student works, publications, dataset, educational resources, or whatever models we create. | | Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
|
69 | |
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. | | Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
|
78OJS 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. | | Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
| 11 | |
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. | | Status |
|---|
| colour | Purple |
|---|
| title | planning |
|---|
|
|
9Long-term preservation using Glacier |
Completed | | | |
Upgrade to Hyrax 3.6
Including code documentation, testing, and adjustments to current customizations. | | | 2024-01-31 |
Bulk upload
Allow for multiple items to be added to ScholarWorks at one time, instead of uploading items individually. | |
RedNotch8 | 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 | | 2023-05-12 |
External repository harvest
Provide the option to harvest descriptive metadata from external repositories into ScholarWorks, so they can be discovered in ScholarWorks as well. | | | 2023-02-01 |
Advanced search
Implement Blacklight advanced search on common fields | | | 2022-07-01 |
Upgrade to Hyrax 2.9
Includes security and bug fixes, IIIF improvements. | | | 2022-04-01 |
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. | | | 2021-10-01 |
Bulk metadata editing
Export all metadata or edit multiple metadata records at once using Excel. | |
20200715Handle integration 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
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.
| |
2020-15 |
Campus-limited view
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. | | | 2020-11-15 |
Long-term preservation using Glacier
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. | | | 2020-07-15 |
Handle service integration
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. | | | 2020-07-15 |
Speed-up migrations
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. | | | 2020-05-15 |
Legend
| Status |
|---|
| colour | Purple |
|---|
| title | PLANNING |
|---|
|
= Enhancement requires planning by the CO before it can be developed.
| Status |
|---|
| colour | Blue |
|---|
| title | DEVELOPMENT |
|---|
|
= Enhancement is in the process of being developed.
= Enhancement is in place for testing on demo system.
= Enhancement is in place on production system.