Harvest Error -- accrualPeriodicity
Overview
How to fix accrualPeriodicity validation errors caused by plain English update frequency descriptions instead of the required ISO 8601 duration codes.
Source
Details
Harvester Guide Pages
| Error Type | Page |
|---|---|
| Getting Started | What is Harvesting? | Understanding Harvest Errors |
| Quick Lookup | FAQ Overview | Quick Reference |
| Date & Time | Date Format Errors (modified, issued) |
| Update Frequency | accrualPeriodicity Errors |
| License | License Field Errors |
| Contact Info | Email Format Errors (contactPoint.hasEmail) |
| Keywords/Tags | Missing Keywords | Keyword Format |
| Missing Fields | Missing Required Fields (modified, keyword, description) |
| File Structure | Transformation Errors (ISO 19115, XML, file problems) |
| Other Issues | Duplicates, Sync Failures, Unrecognized Records |
accrualPeriodicity – update frequency format errors
This error affects about 195 records across multiple sources. It occurs when the accrualPeriodicity field contains a plain English description of update frequency instead of the required code format.
What you see
$.accrualPeriodicity, 'Weekly' does not match any of the acceptable formats: constant value 'irregular' was expected, '^R\/P...'
What this means
The accrualPeriodicity field describes how often a dataset is updated. The DCAT-US schema requires this field to use either the literal value irregular or an ISO 8601 duration code in repeating interval format (e.g. R/P1W for weekly). Plain English values like Weekly, Monthly, or No longer updated are not accepted even though they are descriptively correct.
Common rejected values and their correct replacements
Weekly– useR/P1WMonthly– useR/P1MAnnualorAnnually– useR/P1YAnnual (R/P1Y)– useR/P1Y(the label alone, no parenthetical)Daily– useR/P1DQuarterly– useR/P3MSemiannual– useR/P6MNo longer updated– useirregularArchived– useirregularNever– useirregularNot updated– useirregular
For a full list of ISO 8601 duration codes, see the quick reference.
If you can edit your metadata directly
Replace the plain English value with the appropriate code from the list above. If the dataset is no longer being updated for any reason, use irregular.
If you cannot edit the metadata yourself
Contact whoever manages your agency’s metadata publishing system and tell them:
“The
accrualPeriodicityfield on our datasets needs to use ISO 8601 duration codes instead of plain English descriptions. For example,Weeklyshould beR/P1W,Monthlyshould beR/P1M, andAnnualshould beR/P1Y. Datasets that are no longer updated should use the valueirregular. This is causing validation failures on harvest.data.gov.”