Populate learning objectives for Episode 3 - Accessible

[kmhettne]

Learning objectives are the highest level and focus on what the learner will learn.

[kmhettne]

I like the learning objectives as they stand now in the lesson, but was thinking about adding one that addresses A2. These are the current objectives:

• Understand what a protocol is
• Understand authentication protocols and their role in FAIR
• Articulate the value of landing pages
• Explain closed, open and mediated access to data

I would suggest to add:

• Articulate the value of a metadata longevity plan

[reblake]

I'm curious as to why this episode does not mention repositories (such as found here: https://www.re3data.org/) . That's the first thing I think of when accessibility is brought up. Publishing in an established repository is a great way to make data/software accessible now and into the future.

In this vein, I suggest adding these learning objectives:

1. Identify a suitable repository in which to publish my data/software
2. Verify that metadata is in valid format for chosen repository

[kmhettne]

We talk about repositories and metadata formats in the Findable episode. We try to stay close to the FAIR principles when creating the content and these are the Accessible principles:

• A1. (meta)data are retrievable by their identifier using a standardized communications protocol
• A1.1 the protocol is open, free, and universally implementable
• A1.2 the protocol allows for an authentication and authorization procedure, where necessary
• A2. metadata remain accessible, even when the data are no longer available

Maybe we could fit in something about repositories under A2, but what do you think, should we leave repositories to the Findable episode or do you really want it in the Accessible episode as well?

[reblake]

I understand wanting to stick with the FAIR principles. I'll be a bit more specific with your bullet points above.

• A2: How do you expect users/researchers/data generators to make their "metadata remain accessible..." without publishing their data in an established public repository? What steps do you expect a data generator to take on their own to accomplish this part of FAIR on their own?

This principle (Accessible) includes not only making sure data can be downloaded with authentication, but also persistence/longevity of data/metadata records. Repositories address the "how to" of A1 and A2.

[ccronje]

This could fit in nicely under 'Discussion of tombstones' - perhaps as an activity? To distinguish from the Findable principles it could focus on an example like a retraction? Retractions are important for researchers to find/be aware of in terms of transparency.

On the other hand, the discussion on tombstones could be replaced with a small section on sensitive data https://howtofair.dk/how-to-fair/access-to-data/#sensitive-data - with examples of repositories that facilitate access restrictions (e.g. public metadata, restricted data).