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

Adjust the schema towards transparency issues #337

Open
Jomula opened this issue Aug 2, 2023 · 2 comments
Open

Adjust the schema towards transparency issues #337

Jomula opened this issue Aug 2, 2023 · 2 comments
Assignees

Comments

@Jomula
Copy link
Contributor

Jomula commented Aug 2, 2023

This is partly already done by implementing properties like "open access" or "sustainability plan", but as I was reading an article by Zaagsma (2022), I came across this quote:

To start with, and echoing the call of Hauswedell et al. (2020), we urgently need what could be called digital cultural heritage transparency guidelines that encourage institutions to provide more information about how their digital resources are constituted and were created. Who funded the project? What selection criteria were applied? What classification and metadata schemes were used? How is access provided? What choices were made concerning the interface and search options? And crucially (if often ignored), what relevant offline sources could be of interest to researchers? An increasing number of institutions is beginning to provide (parts of) this information, a development that will hopefully see wide adoption across the GLAM sector. (Zaagsma 2022: 844)

This is an issues especially in the NLS-related area, as due to different reasons, projects are not willing to provide too much transparency, especially not before the project's work is "publication-ready" (e.g. Bibliotheca Arabica). I think that does conflict with Open Scholarship and FAIR principles often required by funding institutions or academic guidelines and should be addressed as such. That being said, we should not use this as a stigma, as there are valid reasons for not being transparent in some cases. But some of the questions above might be interesting to weave into the schema, don't you think?

(Assigned to Xenia, but feel free to change @theodore-s-beers )

@XeniaMonika
Copy link
Collaborator

Very good, thank you! I think this article could be also helpful in the preparation of questions for our interview. I would read it and make notes, but I wouldn´t change the schema before consulting it with you, @theodore-s-beers

@theodore-s-beers
Copy link
Collaborator

I definitely support adjusting the schema to bring these issues into relief. I think it could be done subtly enough that it wouldn't look as though we were being judgmental toward projects that operate relatively less transparently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants