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
The current index has occurrenceIDs in the iptrecordid field. I'm having one of those, "What was I thinking moments." I think it is because this is where the occurrenceID HAD to go in earlier versions of the IPT. In any case, that is where they are, and they can be queried using a pattern that escape quotes the exact string you want to match. For example,
The accepted structure of an API search based on an occurrenceID is of the form shown in the following example:
http://api.vertnet-portal.appspot.com/api/search?q={%22q%22:%22occurrenceid:7108667e-1483-4d04-b204-6a44a73a5219%22}
Parsing of this format fails for occurrenceIDs that have a ':' in the content, as that is used as a keyword designator. For example,
http://api.vertnet-portal.appspot.com/api/search?q={%22q%22:%22occurrenceid:urn:catalog:CRCM:Mammals:13-127%22}
The text was updated successfully, but these errors were encountered: