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

Page provenance #264

Open
tholzheim opened this issue Nov 11, 2021 · 11 comments
Open

Page provenance #264

tholzheim opened this issue Nov 11, 2021 · 11 comments
Assignees
Labels
automation needs automation Migration Migration steps or prerequisites
Milestone

Comments

@tholzheim
Copy link
Collaborator

To keep track of the page creator and responsible main editor of a page we need to add new properties.

  • Property:PageCreator
  • Property:PageEditor

see https://rq.bitplan.com/index.php/Workdocumentation_2021-11-11 for a example application of those properties

@WolfgangFahl
Copy link
Collaborator

You might want to extend the existing userrating.yaml from #170

@tholzheim
Copy link
Collaborator Author

tholzheim commented Nov 11, 2021

Acceptance Criterion:

@WolfgangFahl
Copy link
Collaborator

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.

@WolfgangFahl
Copy link
Collaborator

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.

@tholzheim
Copy link
Collaborator Author

So from the Purgatory a curator can accept the complete series without doing the spreadsheet editing.

@WolfgangFahl WolfgangFahl added this to the 2022-05 milestone Dec 7, 2021
@WolfgangFahl WolfgangFahl added Migration Migration steps or prerequisites automation needs automation labels Dec 7, 2021
@Julian-tib
Copy link
Collaborator

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.

@WolfgangFahl
Copy link
Collaborator

@WolfgangFahl
Copy link
Collaborator

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.

@tholzheim
Copy link
Collaborator Author

For clarification: should the pageCreator and pageEditor only be a user from a "trustedUser/Curator" list.
E.g. pageCreator is first trusted/valid user and pageEditor latest trusted/valid user that edited the page.

Currently only pageEditor is chosen from a curators list. See

Should pageCreator also be chosen from the list?

The list currently consists of the users that edited more than 100 pages excluding the developers

@tholzheim
Copy link
Collaborator Author

Added

Note: Numbers taken from Property page before data rebuild (expected to be a bit higher)

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. NEEDS_CURATION to make the pages with no pageEditor queryable?

Example event of this case: ACIS_2013

@WolfgangFahl
Copy link
Collaborator

see also #271

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation needs automation Migration Migration steps or prerequisites
Projects
None yet
Development

No branches or pull requests

3 participants