You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, cs appears to be a non-documented feature. In the docs, scheme seems to be the documented equivalent. Compare using cs and using scheme in a search for Emory against the LCNAF, and using cs and using scheme in a search for France against the MARC List for Countries.
My suggestion is to change from using cs to scheme.
The text was updated successfully, but these errors were encountered:
Currently, LoC authorities use one of four base urls to limit a search to their subauthorities. These base urls start with "cs:", and produce query urls like https://id.loc.gov/search/?q=Emory&q=cs%3Ahttp%3A%2F%2Fid.loc.gov%2Fauthorities%2Fnames&format=json and https://id.loc.gov/search/?q=france&q=cs%3Ahttp%3A%2F%2Fid.loc.gov%2Fvocabulary%2Fcountries&format=json via the Loc::GenericAuthority#build_query_url function
However,
cs
appears to be a non-documented feature. In the docs,scheme
seems to be the documented equivalent. Compare using cs and using scheme in a search for Emory against the LCNAF, and using cs and using scheme in a search for France against the MARC List for Countries.My suggestion is to change from using
cs
toscheme
.The text was updated successfully, but these errors were encountered: