Previous Updates

• The ehi field has been added to the Monitoring Event schema for Short Term events - this value will be calculated automatically
• The shannonWeiner, speciesCount, and functionalGroupCount fields have been added to the Monitoring Event Site (response) schema for Long Term events - these values will be calculated automatically
• The paddockId field has been added to the Monitoring Event Site (response) schema - this field is automatically set based on the Monitoring Site's paddock when the event is created.
• The notes field has been added to the Evaluation Matrix/Scorecard schema as an optional field - Scorecards are currently read-only
• The completed field was removed from the Monitoring Event Site schema - this field is deprecated and no longer used
• The totalScore field was removed from the Monitoring Event Site input schema - this field is calculated will be returned in the response
• The Monitoring Event-Site endpoints have been made more flexible and only the fields included in the payload will be updated - previously the entire site object was required
• The Monitoring Event-Site endpoint schema has been updated so only Short Term events require the requiredPhotos field - previously this field was (incorrectly) required for all events
• All Monitoring Event-Site endpoints will now return the full Monitoring Event object in the response, including the newly added site - previously only the event-site object was returned
• Monitoring Event schema has been updated - Weather Observations have been moved to the top level observations field and Wildlife Observations have been updated with the correct schema.
• FlexibleArea and BeltArea schemas have been updated with minimum acceptable values for area and distance
• Monitoring Event schema has been updated to add the usableArea and totalArea fields - these values are read-only and are set by the monitoring plan when the event is created.
• Monitoring Plan schema has been updated to add the usableArea and totalArea fields.
• Landbase schema has been updated to remove the usableArea and totalArea fields
• Eco Region schema has been updated to replace the approved field with verification fields
• Scorecard schema has been updated to replace the approved field with verification fields
• When adding a monitoring site to a monitoring event, the siteId will be validated against the landbase's monitoring plan to ensure it is valid
• The v1/landbases/{id}/monitoringPlan endpoint now allows for updating the Long and Short Term siteId arrays individually by sending only the array(s) you want to update
• Paginated endpoints now return a total field with the total number of documents found
• Protections have been added to prevent editing of verified Monitoring Events
• Verification fields have been added to the MonitoringEvent schema for GET endpoints
• The renamed misspelled quantity field to quality in the v1/monitoringevents/{id}/monitoringSites/{id}/forage endpoint
• All paddock endpoints have been moved to the v1/landbases/{landbaseId}/paddocks route from the v1/paddocks route
• The v1/ecoregions/{id}/scorecards route now supports pagination - as a result the endpoint schema has changed
• The v1/landbases/{id}/monitoringsites route now supports pagination - as a result the endpoint schema has changed
• The v1/landbases/{id}/monitoringevents route now supports pagination - as a result the endpoint schema has changed
• Updated the v1/monitoringevents/{id}/monitoringSites/{id}/transects endpoint to be plural (previously was transect)
• Redundant IDs have been removed from payload schemas when they were present in the route (such as landbaseId in the monitoringevent creation payload)