Closed wlpotter closed 1 year ago
Looking back through the data from Box, there are a few difficult cases:
/items/{URI}
string
Cases:
items\/.*
, which will get the 'items/' string, the item key, and anything that may come after it. Extract using regex; substring-after items/
; substring-before-if-contains /
should result in just the item key./
then add back bibl-uri-base.xs:string
should do the trick as a typing error will be raised if the key is an empty string.I've updated the post-processor. Want to test this out with the new data to see if it works or not
Based on tests with the newest data, I have found no failures that slipped through; and on one occasion the typing constraints caught malformed input URIs. So I believe this is fixed.
It looks like the regex for the bibl URI generation in the post-processor needs some work. The regex is too simple to catch and handle all the various formats of a zotero link.
Simplest option would be to make the regex more flexible in catching variants.
Another would be to have a check against an index of existing zotero URIs (maybe use the Zotero API to get a list of valid item keys?)
Needs more thought.