September 13, 2010
ANDS held a Data Capture Briefing in Melbourne on 2 Sep 2010. It was great to see some of the other projects in progress, and that Tardis is a potential platform for some of those projects.
There was also updates on RIF-CS, with version 1.2 coming soon. The updated Service definitions should better meet the MeCAT project requirements.
One aspect that I think needs further thought in RIF-CS is Party lookup. When making entries available for harvesting, Tardis should connect researchers with the collections they were involved with. The lack of reliable automated Party lookup makes this difficult to guarantee.
August 29, 2010
There is now a blog for ANDS (The Australian National Data Service) funded projects at http://adfi.usq.edu.au/ands-partners/. We may move across to the shared blog at a future date, but will stay here for now. I ‘ve added the ANDS blog to the blogroll.
July 26, 2010
As has been highlighted in previous posts, most projects about data publication in the research field have come across the problem that while researchers believe in publishing / sharing data in principle, they have lots of reasons not to do it in practice. This is a much larger problem than can be addressed in one project, so we’ve decided to work around the problem as much as possible by providing access controls within MeCAT that support publishing data immediately, restricting access either indefinitely or until criteria are met, or sharing on an individual basis.
The set of use cases that we’re using as the basis of the Access Control design are listed below.
The Data Owner has the ability to grant and remove access privileges to the data owned. The Data Owner will typically be the Principle Investigator or a representative of the Institution.
- Publicly Accessible
The data is made publicly available immediately, e.g. data that will become part of a reference database.
- Accessible by the Data Owner and assigned team members
Team members may be assigned individually or as a group.
- Access granted by the Data Owner
E.g. as a result of direct contact by another researcher.
- Accessible by anyone at a given physical location, typically the instrument
- Publicly Accessible after an embargo period, e.g. 3 years
- Publicly Accessible after a trigger, e.g. paper is published
- Accessible by facility scientist. Facility scientists typically have access to all data from the instrument they are responsible for.
I’ll cover the design we’re proposing to support these use cases in a subsequent entry, and am interested in any feedback on these use cases.