Transformation process to add project's members

[jachro]

As a renku-graph maintainer, I'd like the triples curation process to enrich the project metadata by adding the project's members.

Acceptance criteria:

• [ ] ~consider using ontology described here; (this looks like it will make things (incl. queries) much more complicated) maybe not necessary~
• [x] create a subscription_category_sync_times table in the event-log DB;
• [x] add a new subscription category for project members synchronisation;
• [x] add categoryName property to the events sent by event-log;
• [ ] create a process on TG to synchronise single projects members;
  • [x] the process to fetch project members from GitLab;
  • [x] the process to find existing members in TS; upsert members which have changed or are newly added (try to find a person by GitLabId and link it to the Project if it exists); unlink members not existing in GitLab as this project members;
• [x] change the POST /events endpoint on the TG to accept members_sync events and direct these events to the member sync process;
• [ ] make TG to subscribe for the members_sync events on the EL;

projects-members-sync.drawio.txt

[rokroskar]

When adding additional elements to the graph model, we should make sure that this is documented and consistent with the SHACL shapes defined for the KG as a whole.

[jachro]

Good point. Although I think that could force us to open our SHACL as e.g. project members could not appear on payloads generated by renku log.

[rokroskar]

What do you mean by "open"? To not enforce shapes? I think a closed shape can still have optional elements. Could be wrong though - @Panaetius will know :)