nathandunn
commented
3 years ago @obsidian83 I had two thoughts on this:
additional status that could be attributed to models that only an admin or role with higher permissions could use
So in addition to the regular curatorial status you would add an admin status, or would you want to restrict the assignment of some statuses to admin only?
If for some reason we can't do that here, you should be able to add comments or key/value pairs that effectively act as a status.
obsidian83
The use case for this functionality is to allow curators/admin staff the ability to check users annotation and verify that it is accurate to their best assessment, putting a status for approval/rejected/pending to already status tagged "finished" models.
For some genomes in VEuPathDB we want to have some level of curatorial oversight especially with the highly curated organisms, so a way to approve a users annotation (mainly functional) would be beneficial. The way I thought this could be achieved is with an additional status that could be attributed to models that only an admin or role with higher permissions could use.
Example Joe Bloggs goes in drags a model to user created track, adds some GO terms and a product description, adds in the metadata and adds the status finished. A curator then goes in, looks at the report of all annotations with the finished status and goes through each annotation, either accepting the annotation as good or incorrect and adds another higher level status to approve/reject it....models with the admin tag are then parsed out and integrated.