...
- Identifiers
- The code is set up to override the item search when an identifier is available in the MARC 024 field for Discogs, specifically 024 7# $a <discogs identifier> $2discogs. Currently, there are only a handful of Discogs identifiers in the 024 but planning is underway to continue adding these data as part of various workflows and possibly also to copy over any Discogs identifiers that already exist in other fields in the metadata. In the meantime, we have the ability to add an identifier to the metadata for any items where the API search may not yield a preferred match.
- Code and description:
- As explained above, the presence of an identifier in the 024 field will prioritize the use of that identifier to retrieve Discogs information.
- There is a separate module for making a call to Discogs and processing results: https://github.com/cul-it/blacklight-cornell/blob/dev/lib/blacklight_cornell/discogs.rb
- Search requests to Discogs use either the identifier or a query which is generated using information from multiple fields in the metadata including title, record label or publisher, and artist
- Results are parsed and information such as authors, notes, contents, and publication information are packaged. Styles are mapped to genres.
- The display for Discogs data is generated using this code: https://github.com/cul-it/blacklight-cornell/blob/2bc9050b63cc331534de6e169cf97c91b900ac44/app/views/catalog/get_discogs.js.erb
- Additional relevant files may be linked here later
- Performance
- When the Solr index includes the Discogs ID, the performance is fine. When it doesn’t, there’s a slight lag due to the Ajax call in the javascript.
- Where is Discogs information used in the search experience?
- Currently, Discogs information is used to supplement the item view and is not being used in the indexing process. As such, keyword searches or facet queries will not utilize this information. We hope to suggest future discussions on how to bring this information into the index and to additional parts of the search experience. We have had some discussions around how bringing in this information for search may be helpful for end-users, but have not planned for this process yet.
...