Access to and what you dont were going to look more

access to and what you don't. We're going to look more at this in lab. So they also talk about the
availability of data, right? So it's both making information about your data available, but also
making the data available. And they talk about it being when we talked about what sort of
licensing is around it, but also reliably accessible, right? And that's why they're pushing for kind of
permanent object identifiers and repositories. They would like data to be made available in
common and documented formats for it. So not using some special format that only you know
how to work with, but making it available in common formats. So other people can easily make
use of it and easily use it to reproduce your studies of raw in quotes, of course. But the idea that
the data as well as kind of any data that's surrounded the data. And often when we're thinking
about data collected in an electronic environment, there's both a kind of payload and the
metadata that's surrounding it, right? And having both of those B document. And so because that
metadata often provides additional information about the conditions of collection. If you can't
provide access to the data, right? And sometimes you might not be able to provide access to it
yourself. For example, you as a researcher were able to get access because you had a particular
relationship with a public health authority or a company, or you went and you signed a contract
that under which you agreed not to actually release the data to anybody else, et cetera. And so if
you can't actually provide access to the data yourselves, they say, provide information about how
others can gain access, right? Because that way you're at least giving them the tools to go and get
the data so that they can reproduce it. If, if we don't have open and readily and ready access, of
course, it may be that you've done all you can, but somebody still can't reproduce it because they
can't get access to the underlying data. And then finally, to the extent you can write this goes to

kind of addressing any legal encumbrances. So being clear, right? Making it available under some
sort of kind of open license could be really useful depending upon the data right there baby, very
few vehicle encumbrances, but to the extent that there are issues that you can document and a
dress to do that. They talk about availability and documentation of the software. And so are you
using software that's open land, reliably downloadable, or is it software that you made yourself?
If it's your own software, raid, share it so other people can use it and can look at it. Is it's software
that can be installed on different platforms. They certainly have a preference for using software
were there isn't like a huge financial outlay in order to access it. They have kind of preferences for
software that is open source, meaning that the code can be inspected. And in particular things,
making sure that things like versioning history or clear. But here's a whole, just a whole list of