NP2021_Package Collection Identifiers
presentationposted on 27.05.2021, 15:29 by Athena Hoeppner, Christine Stohn
Slides from “Knowledge bases and next steps: new and upcoming"
The Package ID: Seeking Sanity through Standards
Content providers often bundle offerings into pre-set collections by subject, year, or some other scope so libraries can select packages that best fit their needs. Publishers also sell individual journals and books, allowing libraries to select content title-by-title. These options provide an effective approach to selling content. However, they produce a confusing, ever-changing tangle in knowledgebases.
Currently, package names are used identifiers, which introduces challenges for knowledgebase providers and librarians. Marketing pages, access platforms, licenses, invoices, and knowledgebases may all use different names for the same packages. Additionally, package names change, differ on various systems, and different bundles often have very similar names.
Knowledgebase providers load the content bundles to serve as the basis for discovery, linking, and ERM processes. Using package names as the identifier complicates always uniquely identify collections. The problem also affects automatic updates to the knowledgebase, in general, or within a specific library’s holdings. Likewise, librarians have a difficult time determining which of the many similar-sounding packages matches their licensed content.
Ultimately, all parties want to ensure that the licensed content is represented and enabled in knowledgebases for discovery and linking. Consistent unique identifiers may offer a way to improve efficiency and reduce confusion.