Page Comparison

This is a template Evaluation for sunsetting services/softwares, as opposed to infrastructurePULFA.

...

1. Identify the Product Owner(s) for the system. 
   Faith Charlton, Christa Cleeton
   
   
2. Define the service that is being considered for sunsetting.
   PULFA is the discovery portal for Princeton University Library Special Collections Finding Aids.  This service has been replaced in production (see 6. on this list).
   
   
3. Determine who is still using this service.
   Special Collections, Library IT for troubleshooting the new service (ie, comparing search behavior in PULFA to PULFAlight).
   
   Researchers communicating expected behavior in the new application when working with Special Collections.
   
4. Determine what other services integrate with or depend on this service.
   
   1. Figgy
   1. Syncing DAOs to Finding Aids EAD
      1. Note: This is turned off.
   2. Syncing Finding Aids metadata to Figgy objects based on container source metadata IDs
      1. Note: Syncing is happening from Pulfalight now.
   3. Virtual Reading Room OARSC viewer
      1. Note: No dependencies on PULFA.
   2. Bento Search
   1. “Finding Aids” bento search relies on PULFA search index to return search results.
      1. Note: No longer true.
   3. EAD SVN service
   1. Versioned EAD XML using SVN
      1. Note: PULFA depended on this for updated EAD content; no longer needed.
   4. ArchiveGrid
   1. https://github.com/pulibrary/pulfalight/issues/786 
      1. Note: this is done; ArchiveGrid is supported with the PACSCL integration feature; see our content in ArchiveGrid https://researchworks.oclc.org/archivegrid/?q=contributor:462&sort=title_sort+asc 
   5. PACSCL Finding Aids
      1. Note: This is done.
   6. CFR Audio Recordings Guestbook
   1. https://github.com/pulibrary/figgy/issues/4317 
      1. Note: We plan to add a click-through agreement feature, but haven't yet. For the immediate access to the collection, we can use OARSC in Figgy to provide access.
   7. Offline finding aids
      1. Note: This has likely been subsumed by OARSC/VRR; checking with Special Collections to confirm.
   8. Kaltura
   1. There used to be manuscripts content in there.
      1. Note: We can keep linking to Kaltura for the time being; all video content in Kaltura will ultimately need to be migrated, but this is not a PULFA integration. 
   9. PUDL
      1. Special Collections is reviewing the handful of ARK links to PUDL: https://docs.google.com/spreadsheets/d/10Th-3YE4GeOv3nlMaA4WufalreSLQ-ZjOqNUQkGXUNM/edit#gid=0
5. Does this service need a successor service?
   PULFA represents a vital service of PUL. A successor service, PULFAlight, has been developed and is available at the production URL here.
   
   
6. Develop successor service(s).
   This service has been replaced in production with PULFAlight, an Arclight-based Finding Aids application.  This transition was done in coordination with the launch of ArchivesSpace as PUL’s archival information management platform, and data source for PULFAlight.
   
   
7. Transition service dependencies as appropriate to successor services or other systems.
   
   1. Are there any critical issues that should influence the decommissioning schedule (ie, end-of-life software, license expiration for a service we hope to retire, etc)
      1. None
   2. How does the decommissioning process impact staff? Are there previously-set project deadlines or training needs that need to be considered?
      1. Decommissioning PULFA will remove the staff’s tool for troubleshooting between the old system and the new system.
         
         
8. Determine an appropriate backup/restore strategy.
   No backup steps required. Unless we have a perfect image of the server or the actual physical server itself, we probably wouldn't be able to get it back up.  All of the necessary data has been migrated to other services.
   
   
9. Execute the decommissioning process.
   To be completed at a later date. 
   
   
10. Record statistics for services sunset, including infrastructure that has been reclaimed and/or decommissioned.
    To be added when the service is decommissioned.