Van experiment naar werking: verschil tussen versies
Uit Knowledge Graph Kunstenpunt
(Replaced content with "Van wikibase.cloud naar een volwaardige instantie: instance requirements, migratie, recurrente werking zie dit rich text document: https://docs.google.com/document/d/1ElbGMINovcQrmTUUrB-h1Ly1n4ky4YkVhZkhhf46fGE/edit#") Label: Vervangen |
(todo lijst van het werk dat er nog ligt) |
||
| (Een tussenliggende versie door dezelfde gebruiker niet weergegeven) | |||
| Regel 1: | Regel 1: | ||
This wikibase started as an experiment on wikibase.cloud, but we are setting up this production environment at kg.kunsten.be We have some work to be done, before everything is completely operational. Here are the work packages and tasks: | |||
=== Finalise setup === | |||
* User management > support needed from professional.wiki | |||
** how do we distinguish between people that can only consult the data | |||
** people that can contribute to the entities (create and edit entities, add statements, ... but no new properties) | |||
** people that can make new properties | |||
** superusers that can also work in the backend and so on | |||
* Are all the relevant packages installed and activated > mr henry / professional.wiki / kunstenpunt | |||
* ... | |||
=== Metadata transfer === | |||
* finalise the metadata transfer from the legacy databases to the wikibase > Tom should be able to handle this | |||
* identify how to map kg.kunsten.be properties and entities to e.g. https://data.vlaanderen.be/doc/applicatieprofiel/cultuurparticipatie/ or wikidata.org > support needed from professional.wiki (what are the good practices here, automate this?) | |||
=== Image transfer === | |||
* also transfer the image files from the legacy databases to the wikibase > help professional wiki? Example REST api call? | |||
=== Rich text transfer === | |||
* also transfer the rich text fields from the legacy database to the wikibase > help professional wiki? Example REST api call? best approach for this, e.g. insite link? | |||
=== Forms === | |||
* create user friendly forms that accumulate a payload of (meta)data that can be sent to wikibase over the API | |||
** UX has already been done > mr henry | |||
** research if we need to build seperate html forms, or if we can use "Page Forms" in wikibase itself? Mr Henry / professional wiki? | |||
=== Databank.kunsten.be === | |||
* create the SPARQL queries to extract the data from the wikibase so that the results can be visualised on databank.kunsten.be > tom can do some, but might need some SPARQL help from professional.wiki | |||
** I'll be starting here <nowiki>https://docs.google.com/spreadsheets/d/1SMGM2KPUFYmCuwSR9ypHU1IXrk2VXwxpedCGH20lQ0k/edit#gid=0</nowiki> | |||
* adjust the data management strategy at databank.kunsten.be to handle wikibase > mr henry | |||
Huidige versie van 29 feb 2024 om 15:23
This wikibase started as an experiment on wikibase.cloud, but we are setting up this production environment at kg.kunsten.be We have some work to be done, before everything is completely operational. Here are the work packages and tasks:
Finalise setup
- User management > support needed from professional.wiki
- how do we distinguish between people that can only consult the data
- people that can contribute to the entities (create and edit entities, add statements, ... but no new properties)
- people that can make new properties
- superusers that can also work in the backend and so on
- Are all the relevant packages installed and activated > mr henry / professional.wiki / kunstenpunt
- ...
Metadata transfer
- finalise the metadata transfer from the legacy databases to the wikibase > Tom should be able to handle this
- identify how to map kg.kunsten.be properties and entities to e.g. https://data.vlaanderen.be/doc/applicatieprofiel/cultuurparticipatie/ or wikidata.org > support needed from professional.wiki (what are the good practices here, automate this?)
Image transfer
- also transfer the image files from the legacy databases to the wikibase > help professional wiki? Example REST api call?
Rich text transfer
- also transfer the rich text fields from the legacy database to the wikibase > help professional wiki? Example REST api call? best approach for this, e.g. insite link?
Forms
- create user friendly forms that accumulate a payload of (meta)data that can be sent to wikibase over the API
- UX has already been done > mr henry
- research if we need to build seperate html forms, or if we can use "Page Forms" in wikibase itself? Mr Henry / professional wiki?
Databank.kunsten.be
- create the SPARQL queries to extract the data from the wikibase so that the results can be visualised on databank.kunsten.be > tom can do some, but might need some SPARQL help from professional.wiki
- I'll be starting here https://docs.google.com/spreadsheets/d/1SMGM2KPUFYmCuwSR9ypHU1IXrk2VXwxpedCGH20lQ0k/edit#gid=0
- adjust the data management strategy at databank.kunsten.be to handle wikibase > mr henry
