SSID mapping

SSID rights represents the primary form of rights mapping. SSID rights are used for A-Z and “Complete” collections where clients select titles from a database or collection.

For example, a client may have a subscription to individual journal titles on a well-known journal platform, the client would select each holding in Client Center that comprises their subscription, (customizing as required).

Rights transfer occurs during the ingestion and indexing process when an identifier in the Summon record ((e)ISSNs or (e)ISBNs) matches an identifier in the KB holding or authority record, if the holding is normalized. When successful augmentation occurs the Summon record is assigned the relevant SSID. At search time Summon will filter the search results, only displaying records assigned SSIDs Summon has determined to be listed in the client's rights profile.

Successful SSID rights augmentation can only occur between sources and KB holdings that list (e)ISSNs or (e)ISBNs.

Note: Should SSID rights mapping provide full rights augmentation between KB and Summon, DBID rights are not typically used. DBID rights are typically used in lieu of SSID rights.

For more information on SSIDs, see 360 KB: Title Identifiers in Title Metadata

DBID mapping

Summon will primarily use DBID rights mapping when the database or collection in KB is known to be non-selectable and clients subscribe to the whole database, i.e. the whole platform.

The collection may represent the whole platform or may represent some criteria based subset of the full collection, i.e. a regional or subject based subscription. 

For DBID rights to transfer to Summon records each Summon record must include metadata to identify the record as part of a KB database or collection. During the ingestion and indexing process, records matching the specific metadata requirement will be assigned the relevant DBID, indicating the record to be part of a specific KB database or collection. At search time Summon will filter the search results, only displaying records assigned DBIDs Summon has determined to be listed in the client's rights profile.

Provided this criteria is achieved, DBID rights will typically be used when:

• Content does not meet KB inclusion criteria – for example video, images or archival content.
• Content does not represent cover to cover full text – for example curated subject based platforms.
• Holdings are unavailable, i.e. provider is unable to provide a title list.
• The KB database holdings and Summon records may not have sufficient identifiers to allow a high percentage of SSID rights mapping. For example, aggregated platforms may include content created before ISSN and ISBN were available or commonly issued. The aggregator may not know the identifier or the content may be grey/ephemeral and not have an identifier.
• Despite our best efforts there is occasionally a disconnect between the identifiers supplied to Summon and KB.

Note: Should SSID rights mapping provide full rights augmentation between KB and Summon, DBID rights are not typically used. DBID rights are typically used in lieu of SSID rights.