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

Archiving the research object #105

Open
Repositorian opened this issue Feb 29, 2016 · 5 comments
Open

Archiving the research object #105

Repositorian opened this issue Feb 29, 2016 · 5 comments

Comments

@Repositorian
Copy link

This discussion is around principles and best practices around archiving of compound research objects, such as the model proposed in everpub

@Repositorian
Copy link
Author

Not clear what the values and principles are around archiving of everpub outputs? Do you envision that individual creators are responsible for archiving? Or repositories? Or institutions? The OAIS service model offers recommendations, so perhaps no need to reinvent the wheel?http://www.oclc.org/research/publications/library/2000/lavoie-oais.html

@khinsen
Copy link
Collaborator

khinsen commented Feb 29, 2016

I see everpub mainly as a toolset, adaptable to various methods of archiving and publishing. We will probably start using GitHub for convenience, and Zenodo for archiving right from GitHub. That's simple and good enough for many use cases. But the toolchain should be easily adaptable to other approaches.

In the long run, the questions you raise do require more careful thought, but I'd happily leave them to experts such as you. If recommendations already exist, that's even better, provided they are reasonable from a user's point of view.

Speaking strictly for myself, I wouldn't want to use anything involving my "institution". The one person I know in my organization who ever asked for permission to publish software is still waiting for a reply... four years later.

@Repositorian
Copy link
Author

There's the rub! From an IP perspective, much of what researchers create can be owned by the institution as the employer. This is the very issue and inconvenient truth being wrestled with in the RDA group on Legal Interop of research data (defined to include all research outputs)

@khinsen
Copy link
Collaborator

khinsen commented Feb 29, 2016

Does the RDA group also address cultural differences between countries? Not so much differences in IP legislation, but differences in the attitude towards the law. Here in France, it is generally accepted that law is theory and practice is something different. I have been told that France is the European champion in the number of laws that are never applied. Even the state itself does not respect its own laws.

@Repositorian
Copy link
Author

The group comprises legal experts from multiple jurisdictions, and addresses a host of issues around legal interoperability of research outputs including IP, moral rights, database protection, and even traditional knowledge. You are most welcome to join, follow, and comment!

https://rd-alliance.org/groups/rdacodata-legal-interoperability-ig.html

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

No branches or pull requests

2 participants