Rework WissKI Signup Form
We collect the data that is necessary for setting up a new WissKI. This can be used in
-
instance configuration (cdi/attic/agfd/wisski#11), -
theming, and -
the distillery information system. -
do we need triplestore and repository info outside system?
Administration - "Metadata"
-
Projecttitle, Department, Supervisors (in case of Diss, BA, MA), Poject-Participants, who is respnsible for Admin -
What kind of Project? BA, MA, Diss, Research Project -
Project Testament: Use of the WissKI (how long, esp. after the end of the project / archive / publication intended), see cdi/attic/agfd/wisski#24 -
After graduation valid contact information to AGFD-Admin. -
Name of the WissKI instance, short description. -
additional modules; do you want automatic updates for them? -
Reuse of the data in apps (if the user already knows) -
Prospected need of memory (i.g. 3D models etc.)
Sysadmin Data
-
Access by Administrator of the AGFD always granted - SSH Shell access?
- account names of admins, initial users
- public or not?
Application-Ontology
-
Name/URL of Application ontology (if there is any) -
Properly documentation of classes of the Aplication Ontology and Publication on GITLab.
Content
-
There should be an agreement that the user is responsible for all content, esp. when publication is intended then the user is responsible to clarify all rights and also what content could be problematic to publish and should take provisions accordingly. -
Should also create content page in the WissKI with information about project and participants and contact information. Should be published.
we collect the data here
-
slug
(the name of the WissKI, needed for setup)
Edited by Tom Wiesing