Response: Value of the resumptionToken argument is invalid. OAI Error: Error Code: badResumptionToken. If your receive this message you should check that your service is currently running and that your base URL matches the requested URL in your warning email. This will typically occurs when your service is offline, or the base URL has changed. The harvester was unable to connect to your data service. Here are some typical errors:įAILURE: Unable to connect- Response Code: 500 : Internal Server error This will typically occur when the Trove Harvester is unable to connect to your service or the connection has dropped out due to inactivity. If you have received a red alert there has been a complete failure to harvest your collection. If you receive this error you may need to check your dataset to make sure the metadata in the correctly contains an OAI: prefix in it's element. Records coming through an OAI feed should have an identifier in the that starts with OAI. This error occurs when the a record's tag does hold an OAI prefix. Error: Document head is not in OAI format This is not a tag /tag> it has an opening but the closing /tag> is missing an angle bracket. this is a tag it has an opening and closing Typically when a record does not contain a tag with an identifier or, when elements in the record output are missing opening or closing tags. Malformed record responses occur when a record is missing an important aspect of the metadata. Record rejected, Processing Step: OaiStep, Reason: Record malformed You may like to check your data to see if it matches Trove's Data Dictionary. The most common occurrence of this error is when records are missing a unique identifier, this will be a specific number that refers to one record in your collection. When you receive this message we advise checking the rate limit of requests to your data service and if possible increasing the allowable amount of requests per minute.Ĭheck for Required Fields- Reason: Failed required field check on fieldĪ required field is a data field that Trove must have in order to process a record correctly. This occurs when a harvest is taking a long time to complete and Trove has made a second request to your service to harvest your data while the first harvest is still running. There is already a harvest running for this contributor This occurs for a range of reasons:Ĭould not start harvest. If you have receieved an amber alert there is an error associated with some aspect of the records in your data output. The most common error occurrences are related to the data in your service or the connection between Trove and your service. If you have received a harvest error message in your email, you may be able to resolve this issue by doing some checks on your data service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |