Snippet - FAIR Accessible #2 - A for Accessible II - Russell

Video thumbnail (Frame 0) Video thumbnail (Frame 442) Video thumbnail (Frame 3294) Video thumbnail (Frame 3544) Video thumbnail (Frame 3759) Video thumbnail (Frame 5072) Video thumbnail (Frame 6329) Video thumbnail (Frame 7843) Video thumbnail (Frame 9748)
Video in TIB AV-Portal: Snippet - FAIR Accessible #2 - A for Accessible II - Russell

Formal Metadata

Title
Snippet - FAIR Accessible #2 - A for Accessible II - Russell
Title of Series
Author
License
CC Attribution 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
2017
Language
English

Content Metadata

Subject Area
Abstract
Keith Russell, ANDS, provides an overview of the key components of accessibility. The FAIR data principles were drafted by the FORCE11 group in 2015. The principles have since received worldwide recognition as a useful framework for thinking about sharing data in a way that will enable maximum use and reuse. This webinar series is a great opportunity to explore each of the 4 FAIR principles in depth - practical case studies from a range of disciplines and organisations from around Australia, and resources to support the uptake of FAIR principles.
Freeware Forcing (mathematics) Authentication Metadata Communications protocol Implementation Metadata
Point (geometry) Authentication Standard deviation Presentation of a group Freeware Identifiability Authentication Materialization (paranormal) Virtual machine Metadata Digital object identifier Open set Information privacy Metadata Software Internetworking Authorization Procedural programming Communications protocol Implementation Communications protocol Condition number
Authentication Point (geometry) Freeware Multiplication sign Authentication Virtual machine Metadata Line (geometry) Metadata Frequency Personal digital assistant Authorization Procedural programming Quicksort Communications protocol Implementation Row (database)
Point (geometry) MIDI Email Information Euler angles Characteristic polynomial Set (mathematics) Open set Metadata Number Category of being Uniform resource locator Latent heat Angle Personal digital assistant Revision control Species Species Quicksort Address space
Point (geometry) Standard deviation Service (economics) Email Standard deviation Service (economics) Information View (database) Virtual machine Set (mathematics) Planning Mereology Revision control Mechanism design Angle Personal digital assistant Revision control Self-organization Quicksort Procedural programming Routing Communications protocol Address space Form (programming)
so first of all I'd like to give a brief introduction about the a in the in the date in the fair data principles and the a stands for accessible so the way it's being described in way force 11 described the principles is that metadata so data and the metadata that
both of them are retrieved by their identifier using a standardized communications protocol so when we talk when retrieved by they or identifier that's the identify we talked about last week so that can be a DOI a handle a Perl something that's persistent and that through by using the do I handle Perl you should be able to get access to the data or the metadata and the protocol to get there which would be open free and universally implementable so the thing to think about there is that it's it's something that is a protocol which is standardized and used by can be used by anybody it's not not something that missus spoke not something that's home built or badly documented with classic examples is HTTP that's a very very normal way of using through internet accessing materials and accessing data it should not require some specialized expensive software another point they make in the data in the in the data principles is that the protocol or should should allow from authentication and authorization present procedure where necessary so this is a common misunderstanding is that when people read accessible they think oh that means I have to make my data open if you actually read the fair data principles that's not what they're saying what they're saying is accessible does not actually have to be open or free but it you you are expected to give exact conditions under which the data are accessible so even the heavenly protected and private data can be made fair um if you implement it properly implement the fair data principles properly then a human being can see that the date is and there may be not openly available but then what steps they need to take to get access to the data and because in the fair data principles
also talked about machine access to data if a machine goes hunting around and finally looking for the data the machine
should be able to recognize that the data is not open and what steps need to be taken to actually get to the data I'll talk about that a little further if
the user selects either the human or the machine has been granted access to the data then it should be accessible through some sort of authentication and authorization procedure substandard procedure the last point they make under the their data principles about being accessible is in the case in the the case in which data is no longer available at least the metadata should be accessible so this is of course not ideal but in some cases it is necessary to actually make take the data down so that could be if consent for use was only for a limited period of time or maybe there's been a legal takedown notice or something along those lines that really make it impossible to no longer make the data available in that case it is valuable to still keep up a metadata record describing the data and explaining that the data is no longer available now just to reinforce that
accessible does not always have to be open there are clear cases in which data can not be made openly available obvious example is where data refers to human beings and specific characteristics of those human beings like information about their health their income religion attitudes political persuasion all that sort of stuff that's not the sort of information you can make publicly available other examples and that's probably worth remembering is that there are other sets of data so for example threatened species the location of where threatened species are can MIDI data which is not something you want to make openly available because that could mean that the last few of those species are hunted down or collected famous example the wall of my pine it's a location of that
of those specific species you need to be protected so finally the another example where data cannot always be made openly availables whether our commercial interests in the data and maybe the metadata Ammy shared but the data itself is sensitive well is there are commercial interests around that and in that case it would not be appropriate for that to be made open available when you when considering making data accessible we do argue to make it as accessible as possible and as openly available as possible possible angle there is just to provide the metadata as it's the arting point if the risk cannot be made available at least the metadata slightly more useful perhaps is making it available through mediated access and in that case it's valuable to be clear about how the user can actually get access and that can be through by providing an email address name telephone number and if for example the
user has to go through an ethics procedure to get access to the data then clearly describe that ethics procedure and what sort of information is required to apply for that it to apply for that ethics procedure so I was talking about the immediate access and about providing information about who to contact if you want to get access to the data one thing to keep in mind there is if you are if you list a person or a person within the organization have a think about whether that person is ever going to leave if that's a researcher if they're going to another organization have a fallback have some sort of mechanism to make sure that or maybe more general email address so that when that data custodian leaves somebody else can at least answer the question and grant access to the data another possible angle in making data accessible is make creating a de-identified version of the data and making that public as long as it's properly the identified and that can be useful for certain data users at least have a better view what's in the data set and for some purposes that a de-identified version can be enough finally a good point to keep in mind is if you do want to make the data accessible plan for this thing you could send forms because coming back afterwards and trying to get consent is not easy another angle worth keeping in
mind and that's something I've invited a gene bow to to talk about more is making data accessible Campton be through various routes and various protocol and in some cases it doesn't make sense to have a large data set available through download in some case it can make much more sense to actually have services over the data which allow the users to interrogate parts of the day to pull in parts of the data that are much more specific and much and answer their requests and that can be for a human being but especially for a machine that can be really useful so one thing to keep in mind there you need some sort of community agreed standards around that
Feedback