DRS Legacy Support FAQ

Q: Is DRS going away?

A: No, the Digital Repository Service (DRS) is not going away.  The Service remains (and will remain) a strongly supported core Harvard Library function.  However, the underlying software system currently implementing that function will be replaced in order to ensure our longstanding high levels of service reliability, efficiency, and sustainability.  This is a standard IT process that happens periodically across the lifespan of all software products.

Q: Who is responsible for the DRS?

A: The Digital Preservation Services team (DPS) in HL Preservation Services exercises the business ownership role for the DRS, supporting and advocating for the digital preservation and stewardship needs, goals, and aspirations of HL and University curators and collection managers.  You may contact DPS at digipres@hu.onmicrosoft.com.

Technical and operational responsibility for the DRS is held by HUIT Library Technology Services (LTS), ensuring that the system is highly available, robust, and sustainable.  You may contact LTS at https://harvard-lts.libanswers.com/drs.

Q: What is “DRS Futures”?  What is “DRS Legacy”?

A: DRS Futures refers to the future state of the DRS service after the replacement of its underlying software system.  More information about the Futures implementation project is available at https://sites.harvard.edu/drs-futures/ or contacting the project team at drs-futures-feedback@HU.onmicrosoft.com.

DRS Legacy refers to the current system implementation of the DRS.

Q: What is the timeline for the transition from DRS Legacy to Futures?

A: The initial Discovery phase of the DRS Futures project took place from July 2022 through March 2023.  The current Planning phase, during which potential solutions are being evaluated and one will be selected, will complete in December 2023.  The final Implementation phase, during which the development and migration will be planned and executed, will run from January 2024 through June 2025.  More information is available at https://sites.harvard.edu/drs-futures/timeline/ and as always, we will be providing consistent, robust communication throughout these phases.

Q: How much longer will the DRS Legacy software system be supported?

A: The current DRS Legacy system will continue to be supported until the new Futures solution has been moved into production operation (which will take place during the Implementation phase, explained in the question above).

There may be a short transition period when both Legacy and Futures systems are running in order to facilitate the final migration of all Legacy content to the Futures system.   All existing Legacy workflows will be supported until the transition period, when certain Legacy functions may be constrained.  Up to and during the transition period, critical issues or disruption in Legacy service will continue to be given immediate attention.

Q: While we are awaiting DRS Futures, what kinds of issues will be addressed?

A: DRS Legacy is currently, and will continue to be, in maintenance mode to address immediate problems or conditions that impinge on routine use.

Planning for and implementing the transition from the Legacy to the Futures DRS is a complex undertaking requiring significant time and attention from DPS and LTS.  Consequently, no new enhancement requests for the DRS Legacy software system will be acted upon. The current backlog of enhancement requests has been collected by the DRS Futures team as part of the DRS Futures project discovery phase and added to the DRS Futures User Requirements Catalog.

Q: What is the difference between maintenance and enhancement?

1. Maintenance is the process of ensuring that a software system functions as expected, including correcting critical defects or service interruptions. An enhancement involves adding new capabilities to an existing system, such as addressing non-critical problems, adding new reports, or implementing new service functions. If you have any doubt regarding whether a particular newly arising issue is a bug or an enhancement, please contact the LTS Support Team at https://harvard-lts.libanswers.com/drs.

Q: How can I get refresher training on the Legacy DRS?

A: Submit a ticket through https://harvard-lts.libanswers.com/drs. The LTS Support Team is always interested in helping DRS users stay current on using the service.

Q: What about training on DRS Futures?

A: In-person and virtual training, as well as on-demand resources and documentation, will be offered as an integral component of the transition from Legacy to Futures. Information about and access to these materials is expected in 2025.

Q: How much lead time will I have to prepare for the implementation of the new Futures system?

A: We are planning to provide the DRS user community with at least 6 months to prepare their tools, workflows, and data for the Futures system.  This scheduling will become clearer as the Futures project moves into its final Implementation phase in 2024.

Q: What will happen with all the content I already have in DRS Legacy?

A: All retrospective content will be migrated forward automatically into the Futures software system.  This process will include extensive verification to ensure that no information is lost or damaged.

Q: Which current DRS components will be replaced as part of the DRS Futures project?

A: All core preservation functions as well as Batchbuilder, the online Web Admin interface, and connections with external discovery & delivery systems and other repositories such as DASH and Dataverse will be replaced. Content delivery platforms are out of scope for this project.

Q: How will the content delivery services project be impacted by the DRS Futures project?

A: Content delivery platforms (collectively referred to as Media Presentation Services) will continue to offer user access to objects preserved in the DRS. Replacement and enhancement of these services is otherwise outside the scope of the DRS Futures project, which focuses on replacing the preservation system and functions.  The Futures system will integrate with all of our delivery platforms.

Q: I have an issue or a question concerning the Legacy DRS. How can I get help?

A: Submit a ticket to the LTS Support Team through https://harvard-lts.libanswers.com/drs

Q: How can I find information about known issues with the Legacy DRS?

A: Please refer to the DRS Known Issues wiki page: https://harvardwiki.atlassian.net/wiki/display/LibraryStaffDoc/DRS+Known+Issues  

Q: Will issues relating to the Viewer be listed on the DRS Known Issues wiki page?

A: No, as that page is limited to issues with the DRS itself. However, we are exploring the possibility of creating Known Issues pages for other systems that DRS supports.

Q: Can I see my submitted tickets?

A: Unfortunately, this functionality is not available in LibAnswers.

Q14: Can I see other teams’ submitted tickets?

A: No, but between the “known issues” list and the DRS User Community meetings, we hope to provide transparency into open issues.

Q: How can I stay connected with the DRS Legacy technical team, technical priorities, and current activity?

A: Attend the DRS User Community meetings! We anticipate that a cadence will be roughly every 2 months, with a break during the summer.

Q: How can I stay connected with the DRS Futures project team, progress, and current activity?

A: Please visit the project website, https://sites.harvard.edu/drs-futures/news-events/, for continual updates on progress and plans.  You may also contact the project team at drs-futures-feedback@HU.onmicrosoft.com.