Skip to content
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

Open
gubuntu opened this issue Jul 27, 2022 · 10 comments
Open

RF18 Report errors with a metadata record or its underlying datasets #263

gubuntu opened this issue Jul 27, 2022 · 10 comments
Assignees

Comments

@gubuntu
Copy link
Contributor

gubuntu commented Jul 27, 2022

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.

@gubuntu gubuntu added this to the Deployed, tested and accepted milestone Jul 27, 2022
@gubuntu
Copy link
Contributor Author

gubuntu commented Jul 28, 2022

@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 Samweli self-assigned this Aug 1, 2022
@gubuntu
Copy link
Contributor Author

gubuntu commented Sep 5, 2022

@Samweli this has been 'in progress' for a month, what's the blocker?

@Samweli
Copy link
Collaborator

Samweli commented Sep 5, 2022

@gubuntu I was focused working on #218 before my leave, I'm back in office today, I'm currently making changes to the #218 related issues(there is a new validation schema) and then I ll shift to work on finishing this, thanks.

@Samweli
Copy link
Collaborator

Samweli commented Sep 7, 2022

@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.

Error reporting workflow
emc-error_reporting_workflow drawio (1)

@ntobe-nyuswa
Copy link
Collaborator

ntobe-nyuswa commented Sep 7, 2022

@vutomim, please see the workflow above

@vutomim
Copy link
Collaborator

vutomim commented Sep 8, 2022

@Samweli and @ntobe-nyuswa

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.

@Samweli
Copy link
Collaborator

Samweli commented Sep 8, 2022

Thanks for the information @vutomim

A notification sent to the user and NSIF.

Is this notification sent after the data custodian has confirmed the error or after they republish the record?

@vutomim
Copy link
Collaborator

vutomim commented Sep 8, 2022

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).

@Samweli
Copy link
Collaborator

Samweli commented Sep 13, 2022

As discussed with @vutomim the below is the target workflow

image

@Jeremy-Prior
Copy link

An Error Report created today (17/03/2023) does not appear in the list of error reports awaiting review (even on an admin profile.
issue263_1
So the functionality to create an error report is there but the report does not show up for moderation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants