Tip |
---|
Rank projects here. |
...
Enhancement | Status | Priority | Updated | ||||||
---|---|---|---|---|---|---|---|---|---|
About us page |
| 1 | 2023-11-02 | ||||||
Usage stats (reporting) |
| 2 | 2024-06-18 | ||||||
Usage stats (campus) |
| 3 | 2023-11-02 | ||||||
Campus landing page |
| 4 | 2023-06-01 | ||||||
ORCID bulk import |
| 5 | 2023-06-01 | ||||||
OJS > Samvera integration |
...
| 6 | ||||||||
Save submission as draft |
| 7 | |||||||
Top-level facet for model |
| 8 | |||||||
Share-your-paper integration |
...
, 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. |
| 9 | |||||||
Collection search |
...
| 10 | ||||||||
Email alert enhancements |
| 11 | |||||||
Completed | |||||||||
Usage stats (works) |
| 2024-06-18 | |||||||
Upgrade to Hyrax 3.6 |
| 2024-01-31 | |||||||
Bulk upload |
| 2023-05-12 | |||||||
External repository harvest |
...
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.
...
Usage stats enhancement / robust statistical reports
Create easy to use statistical reports that are easy to download and share.
...
Batch uploading new works
Create functionality to allow for multiple items to be added to ScholarWorks at one time, instead of uploading items individually.
...
Batch metadata editing
Create functionality to allow for multiple metadata records to be edited at once. (Possibly export the metadata to excel and then import the cleaned up data after?)
...
Batch metadata export
Create the option to export multiple metadata records in one batch. (Possibly to excel?)
...
Top-level facet for model
e.g., student works, faculty publications, dataset, educational resources, or whatever models we create.
...
Email alert enhancements
Email stakeholders when certain actions happen within ScholarWorks. Melissa Seelye (Unlicensed) , could you please add what you meant for functionality here?
...
Search engine optimization
Configure ScholarWorks so that search engine crawlers are accurately crawling and indexing the site. For example, it would be helpful if items from ScholarWorks made it into Google Scholar more readily.
Previous projects
...
...
| 2023-02-01 | ||||||||||||||
Advanced search |
| 2022-07-01 | |||||||||||||
Upgrade to Hyrax 2.9 |
| 2022-04-01 | |||||||||||||
ORCID links |
| 2021-10-01 | |||||||||||||
Bulk metadata editing |
| 2021-09-01 | |||||||||||||
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. |
| 2021-05-07 | |||||||||||||
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 | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|