The Project Admin Account for Production
Each project on a production server has one project admin account for data uploads. DaSCH uses the project admin account for all work on the data of the project on production.
Account Scheme
- Email:
<shortname>@admin.dasch.swiss, where<shortname>is theshortnameof the project. - Role: project admin of the project.
DSP-APP shows the project admin account as the creator of the uploaded data. If you make your own data model, agree on the username, given name and family name with DaSCH.
Who Creates the Account
The person who sets up the data model also creates the account:
- If the DaSCH Research Data Unit (RDU) sets up the project, RDU creates the account and owns it.
- If you make your own data model, you create the account.
In both cases, add the account to the
users section of the JSON project file.
uvx dsp-tools create then creates the account together with the project.
The account needs ":admin" and ":member" in its projects.
If you use excel2json, add the account to the "Users" sheet
with the role projectadmin.
On the prod-like servers api.dasch.swiss, api.rdu.dasch.swiss and api.stage.dasch.swiss,
create stops if the JSON project file has no such account.
create stops as well if the account has no admin rights in its projects.
On all other servers, create only shows a warning.
create --validate-only runs the same check, if -s is set to the target server.
If the project exists already, create still needs the account in the JSON project file.
If the account exists in DSP-APP already, write its username and email exactly as they are in DSP-APP.
Example of the account in the JSON project file:
{
"users": [
{
"username": "<agreed username>",
"email": "<shortname>@admin.dasch.swiss",
"givenName": "<agreed given name>",
"familyName": "<agreed family name>",
"password": "<password>",
"lang": "en",
"projects": [
":admin",
":member"
],
"status": true
}
]
}
Use on Production
On production, a DaSCH system admin runs create, because create needs the credentials of a system admin.
After create, DaSCH uses the project admin account for these commands:
Authorship of the Data
DSP-APP shows the project admin account as the creator of the data. The creator is only the account that uploaded the data. It does not show who made the data. Because DaSCH uploads all data of the project with the same account, the creator is the same for all resources.
The author is the person or the institution that made the content, for example
the researcher who transcribed a letter or the photographer of an image.
DSP does not get the authors from the account.
If the XML file gives no authorship, the data has no author in DSP.
Then the users of the data cannot see whom to give credit to, and cannot cite the authors correctly.
The project default default_data_authorship does not change this on its own:
xmlupload applies it only if the XML file tells it to.
Give the authorship, the copyright holder and the license in the legal metadata of the XML file:
- Multimedia assets: the attributes
authorship-id,copyright-holderandlicenseon<bitstream>and<iiif-uri>. - Resources: the attribute
authorship-idon the<resource>element. - Definitions of the authors:
<authorship>. - Project defaults:
default_data_authorship. The attributeuse-project-default-resource-authorshipon the<knora>element applies the project default to all resources without their ownauthorship-id.
If you use the xmllib, see Setting the Authorship of a Resource.