Evaluation for sunsetting PULFA.

Identify the Product Owner(s) for the system.
Faith Charlton, Christa Cleeton
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).
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.
Determine what other services integrate with or depend on this service.
1. Figgy
2. Bento Search
3. EAD SVN service
4. ArchiveGrid
5. PACSCL Finding Aids
  1. Note: This is done.
6. CFR Audio Recordings Guestbook
7. Offline finding aids
  1. Note: This has likely been subsumed by OARSC/VRR; checking with Special Collections to confirm.
8. Kaltura
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
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.
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.
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.
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.
Execute the decommissioning process.
To be completed at a later date.
Record statistics for services sunset, including infrastructure that has been reclaimed and/or decommissioned.
To be added when the service is decommissioned.

Browser not supported