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
I'm not familiar with the history or status of http://sciencebase.gov/vocab/identifierScheme and https://www.sciencebase.gov/vocab/category/item/identifier. It seems that each works sometimes (for example, query_sb_doi('10.5066/F7ZC80ZP') works with the second scheme). Are there other possible/probable schemes for DOIs that should also be included? query_sb_doi should probably turn up items with DOIs under any sensible scheme that can exist in SB, though it's possible that the best fix for this is on the SB side (to update items that use an old scheme, if one of the above is deprecated) rather than on the sbtools side. Current SB & sbtools maintainers, please weigh in on the desired approach.
The text was updated successfully, but these errors were encountered:
It looks to me like there are more possible Schemes for DOIs than currently recognized by
query_sb_doi
. For the use case of trying to query for https://www.sciencebase.gov/catalog/item/570bbfa7e4b0ef3b7ca0294a by DOI:using the scheme embedded in
query_sb_doi
:using the scheme I see in the Identifiers section of https://www.sciencebase.gov/catalog/item/570bbfa7e4b0ef3b7ca0294a:
I'm not familiar with the history or status of http://sciencebase.gov/vocab/identifierScheme and https://www.sciencebase.gov/vocab/category/item/identifier. It seems that each works sometimes (for example,
query_sb_doi('10.5066/F7ZC80ZP')
works with the second scheme). Are there other possible/probable schemes for DOIs that should also be included?query_sb_doi
should probably turn up items with DOIs under any sensible scheme that can exist in SB, though it's possible that the best fix for this is on the SB side (to update items that use an old scheme, if one of the above is deprecated) rather than on thesbtools
side. Current SB & sbtools maintainers, please weigh in on the desired approach.The text was updated successfully, but these errors were encountered: