-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RF18 Report errors with a metadata record or its underlying datasets #263
Comments
@ricardogsilva marked this as partially complete. I think it is implemented on the backend and just needs to be implemented on the front-end? |
@Samweli this has been 'in progress' for a month, what's the blocker? |
@ntobe-nyuswa below is the suggested error reporting workflow for faulty metadata records. Please let me know if you and Vutomi are okay with it before I proceed and add the implementation for it in the system, thanks. |
@vutomim, please see the workflow above |
The user will identify an error on the record Fill the form and provide sufficient description of the error (may include submitting a snapshot) as well as record UID, Submits The NSIF will review the submission, if it is complete, forward the request for review of record to custodian The custodian will receive and review a record. If satisfied that it is an error from their side, retrieve and update the record and republish. A notification sent to the user and NSIF. |
Thanks for the information @vutomim
Is this notification sent after the data custodian has confirmed the error or after they republish the record? |
Preferably after republishing, but you'll there are time where there might not be a need to republish (e.g. if the custodian is of the opinion that it is not an error on the record). |
As discussed with @vutomim the below is the target workflow |
When a fault in a metadata record or in the underlying dataset(s) is detected, any user shall be able to notify the responsible party for the metadata record in order to inform him of the problem. This shall be done by means of submission of an electronic form that complies with Form D (as shown in Annexure D).
Refer also to the workflow defined in 'SASDI Processes.pdf' and reflect your implementation plan in our DCPR draw.io diagram for review before implementing.
The text was updated successfully, but these errors were encountered: