-
Notifications
You must be signed in to change notification settings - Fork 3
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
Page provenance #264
Comments
You might want to extend the existing userrating.yaml from #170 |
Acceptance Criterion:
|
The derivation of PageCreator and PageEditor will IMHO need some heuristics. Having the properities and being able to set them via a template and or semantic markup seems to be a good solution. IMHO the #236 should also be able to set these if the curator wants to do manual modifications. |
For mass-imports we need to define who should be the PageCreator and PageEditor in these cases. IMHO there should be a workflow in which a curator checks the massimport and the curator's account would then be referenced. |
So from the Purgatory a curator can accept the complete series without doing the spreadsheet editing. |
Für die Migration der Daten in das neue System wäre es sehr wichtig, dass für alle Event- und Eventseries pages im RWTH Clone diese beiden Properties gesetzt sind. |
https://confident.dbis.rwth-aachen.de/or/index.php?title=Property:Page_creator now has the raw values which might still need to processing that we proposed to know the role of the creator and rate it. |
For clarification: should the pageCreator and pageEditor only be a user from a "trustedUser/Curator" list. Currently only pageEditor is chosen from a curators list. See
Should pageCreator also be chosen from the list?
|
Added
Should a special value be set as pageEditor in the cases were no pageEditor could be determined (user was not list of users from the excel sheet). i.e. Example event of this case: ACIS_2013 |
see also #271 |
To keep track of the page creator and responsible main editor of a page we need to add new properties.
see https://rq.bitplan.com/index.php/Workdocumentation_2021-11-11 for a example application of those properties
The text was updated successfully, but these errors were encountered: