Changing a library name across all systems and services requires analysis from both LTS and HL business owners. Some changes require development cycles to complete, and dependencies among tasks determine the order in which changes can be applied. Due to the number of resources required, LTS requires advance notice of at least 3 months to both validate the items in the checklist, add in tasks for new systems, and schedule resources.
Records in external aggregations such as DPLA will not reflect the name changes made in Harvard systems until the partner reacquires the affected records.
Request received May 16, 2022 via FP 43144
This summer, HKS Library & Knowledge Services will be changing its name to “HKS Library & Research Services.” We have set June 6 as our changeover date... there are a number of places where it makes sense for us to be referred to as “Harvard Kennedy School,” though. I went through the Wiki list and denoted which systems should use which name. (I’ve left out systems where I’m pretty sure they don’t apply to us, so please correct me if I’m inadvertently missing anything.) The one potentially weird thing is that for Springshare products, we’d like to be referred to as “HKS Library & Research Services” in LibAnswers and LibGuides, but as “Harvard Kennedy School” in LibCal.
...
Active projects
...
Will that be possible?
Harvard Kennedy School (i.e. no change – CB)
* All Alma systems
* Acorn
* Aeon
* ArchivesSpace
* Barcode
* Borrow Direct
* CURIOsity
* DPLA
* DRS
* Digital collections catalog
* HOLLIS
* ILL
* JSTOR Forum
* LibCal
* LibraryCloud
* OCLC
* Ordering via vendor systems (e.g. GOBI)
* Scan & Deliver
* Storage facilities
HKS Library & Research Services
* Gift agreements –
* HART –
* HL website - CB forwarded to harvard_library
* LibAnswers & LibGuides. – CB forwarded to Reed.
NOTE - because the name is remaining unchanged in most places, the table below has not been filled out.
Type | Task | System | Phase | Who |
---|---|---|---|---|
Planning | ||||
Communication | General announcement to hlcomms | Planning | Library Lead | |
Planning | Project team kickoff meeting with Library, Comms, HL, and LTS project members | Planning | Library Lead | |
Planning | LTS will create wiki page for project that tracks all mapping information, timelines, and decision points and share with stakeholders. | Planning | LTS (Systems and Support Lead) | |
Local Tasks | ||||
Technical Implementation | ||||
Alma Library Management Configuration | Update library name in configuration
| Alma | Implementation | LTS (Systems Librarian) |
Alma Scripts |
| Alma | Implementation | LTS (Systems Librarian, DevOps) |
Alma Analytics |
| HART | Implementation | LTS (Systems Librarian) |
Alma Items updates |
| Alma | Implementation | Library Staff/LTS (Systems Librarian) |
ALMA--Updating catalog records and textual notes referring to owning library |
| Alma | Implementation | Library Staff/LTS (Systems Librarian) |
Alma Spine Labels |
| Alma/SpineOMatic | Implementation | Shelf Prep/Local processing unit |
ACORN |
| Acorn | Implementation | WPC ACORN Admin |
Aeon |
| Aeon | Implementation | LTS Aeon support staff or the HL Aeon primary contact (TBD) |
ArchivesSpace |
| ArchivesSpace | Implementation | LTS (Metadata Analyst) potentially also LTS (Developer) |
Barcodes |
| (n/) | Implementation | Library Staff/Shelf Prep/Local processing unit |
Borrow Direct |
| BorrowDirect | Implementation | LTS (Systems Librarian), HL AS RS Lead |
Class Request Tool |
| CRT | Implementation | CRT "admin" user in the library/archive |
Colonial North America |
| CNA | Implementation | HL Digital Collections Lead |
CURIOSity |
| CURIOSity | Implementation | HL Digital Collections Lead |
DPLA |
| DPLA | HL Digital Collections Lead | |
DRS |
| DRS | Implementation | LTS (Developers/OPS) |
DRS--Updating object-specific information |
| DRS | Implementation | Content Owners will need to decide if manually changing METS and Custom Caption Unit names in each object is necessary. |
DRS – Delivery Services |
| DRS | Implementation | Content Owners will need to decide if manually changing METS and Custom Caption Unit names in each object is necessary. |
E-bookplates |
| Bookplate Script | Implementation | Library Staff/LTS (Systems Librarian) |
Gift Agreements (and other legal documents) |
| (n/a) | Implementation | Library Staff/OGC/Kyle Courtney |
HART |
| HART | Implementation | LTS (Systems Librarian) |
Harvard Library Website |
| HL Portal | Implementation | HL Communications Teams |
Harvard Digital Collections Catalog |
| Harvard Digital Collections | Implementation | HL Web Team |
HOLLIS |
| Alma | Implementation | LTS (Systems Librarian) |
ILL |
| ILLiad | Implementation | LTS (Systems Librarian), HL AS RS Lead |
JSTOR Forum |
| JSTOR Forum | Implementation | LTS (Metadata Analyst) or library, Developer for reharvest. |
LibAnswers, LibGuides |
| SpringShare Systems | Implementation | HL SpringShare Lead |
Library of Congress |
| LoC | Implementation | LTS (Metadata Analyst) or library |
LibraryCloud |
| LibraryCloud | Implementation | LTS (Metadata Analyst, Developer) |
OCLC |
| OCLC, Custom Scripts | Implementation | LTS (Metadata Analyst, Systems Librarian) or library |
Ordering via vendor systems |
| GOBI | Implementation | LIbrary/ITS |
Scan & Deliver |
| ILLiad | Implementation | LTS (Systems Librarian), HL AS RS Lead |
Storage Facilities |
| LAS, SCSB, Website | Implementation | HL Access Services |
Post | ||||
LTS wiki page updates |
| Wiki | Post | LTS |
Local wiki page updates | Update local documentation as needed | Wiki | Post | All stakeholders |