@excelsior
As noted in discussion for #929 , it would be useful to be able to track where all processes related to publishing a resource may not have been completed.
The suggestions included:
- adding a property to the envelope for tracking status
- A single property may be fine where steps are sequential, but would a different approach be needed for async activities?
The actions for a consumer may vary depending on what tasks are outstanding.
Based on recent issues, the completion of all tasks that will result in a /resources/ view returning a completed resource is the most important.