Summary
A new practice for identifying "Databases" in HOLLIS+ was implemented in the summer of 2016. This will affect resource type display and faceting (resource types only). It is not a substitute for appropriate subject cataloging.
In order for a record to appear as a "Database" in HOLLIS+, the Aleph NET holding should include the collection code DBASE, instead of GEN:
852 |b NET |c DBASE
This should only be used for resources available Harvard wide, via the internet.
"Databases" in HOLLIS+ can also be faceted by the resource type identified in the LDR, as defined in the HOLLIS+ resource type definitions.
For example, JSTOR can be found as either a "Database" or a "Journal." It will appear in the search results with the "Database" icon.
This is unrelated to the Databases "tab" in the top omnibar which brings users to Metalib.
When is an e-resource a database? When is it not?
Databases are usually integrating resources. Cataloging is based on the current iteration. The DBASE code may be applied to online resources available Harvard wide, that represent collections of materials that can be searched within the database platform, such as a collection of journal articles (e.g. JSTOR) or an indexing service (e.g. EBSCOhost).
E-journals are normally NOT databases. Do not change collection code MRCIT to DBASE.
Database indicator in ERIN
The Database indicator is selectable for New E-Resource requests in ERIN. Staff will select "This is a Database" when they want the resource to appear as a Database and be included in the Database facet.
Unsure whether your resource would be considered a database? Consult with your E-Resource coordinator (listed at E-Resources Unit) for guidance.
ERIN notification for databases
For staff cataloging e-resources, the collection code will be indicated in the body of the message with Subject: "ERIN: Request for Cataloging with Database Collection Code" as follows:
- in Aleph, complete the cataloging using 852 $$b NET $$c DBASE in the holding record.
Sample holdings record
