 Okay, so next another Andrew, Andrew Maynett to talk about the NIF experience. Alright, so I'm going to talk about National Trusted Data Repositories for the National Imaging Facility. So my name's Andrew Maynett, I'm a NIF Informatics Fellow at the Centre for Microscopy Characterisation Analysis at the University of Western Australia. So very quickly what is NIF? The Australian National Imaging Facility is a $130 million project providing state-of-the-art imaging capability of animals, plants and materials for the Australian research community. A little map there to the right shows the various nodes of the National Imaging Facility around the country. Now why is NIF interested in trusted data repositories? Well the imaging equipment such as MRI, PET, CT scanners are capable of producing vast amounts of valuable research data. So we're interested in maximising those research outcomes and to do so the data must be stored securely and must have its quality verified and should be accessible to the wider research community. From the core trust sealed point of view why trusted data repositories? Well firstly to be able to share data. Secondly to preserve the initial investment in collecting that data. Thirdly to ensure that the data remain useful and meaningful into the future. And the last one importantly is that funding authorities are increasingly requiring continued access to data that's produced by projects they fund. Alright now I want to talk specifically about the NIF RDS and trusted data repositories project officially titled delivering durable, reliable, high quality image data for the National Imaging Facility. Now broad aim of the project was to enhance quality, durability and reliability of data that's generated by the NIF. Now by quality we mean the data has to be captured according to what we call the NIF agreed process. Durable means that the data has to have guaranteed availability for 10 years and reliable means that the data has to be useful for future researchers. So it has to be stored in one or more open data formats and with sufficient evidential metadata so we know how it was created, what the state of the instrument was at the time of creation and so on. The NIF nodes involved with the University of Western Australia, University of Queensland, University of New South Wales and Monash University. And in the project we limited our scope to MRI data but essentially the results are generalizable to other modalities and in fact we've already progressed to micro CT. So key outcomes from the project include the NIF agreed process to obtain trusted data from NIF instruments. I'll talk more about that shortly. The second is requirements necessary and sufficient for a basic NIF trusted data repository service. The third were exemplary repository services across all four participating nodes. And then the last one were self assessments against the core trustworthy data repositories requirements from core trust seal. So the NIF agreed process requiring high quality data. This essentially lists requirements that have to be satisfied to obtain high quality data which we call NIF certified data that's then suitable for ingestion in a NIF trusted data repository service. We mandate the repository data must be organized by project ID because project IDs will persist with time whereas user IDs don't, users come and go. Now to be NIF certified the data must have been acquired on a NIF compliant instrument or about that shortly. It has to possess NIF minimal metadata so that includes cross reference to relevant instrument quality control data. It has to include the native data generated by the instrument in proprietary format and include conversions to one or more open data formats. So the requirements for a NIF trusted data repository service we drew upon the core trust seal requirements in the left column that you see there. And additionally added some NIF requirements. So one of them you've seen already the project ID requirement. But we also require an instrument ID requirement. Quality control requirement, authentication by Australian Access Federation requirement. Interoperability that is we should be able to upload data from one repository to another redeploy ability. It should be possible to deploy the service from one NIF node to another and a service requirement that essentially we have a help desk responding to requests regarding the repository. So in a nutshell if we have a look at this diagram if we can concentrate on the right hand side. If we have we've got the four sites UWA, UQ, UNSW and Monash so true that at that particular site represents the trusted data repository. Login is by the Australian Access Federation so that means on any of the sites it will direct you back to your institutional login page and use institutional credentials. As I mentioned before data sets are organized by project ID. A data set is associated with an instrument and provided the NIF agree process has been followed then a NIF certification flag indicating that it is certified is also included with the data set. And the repository has a record for the instrument. The instrument itself is linked to another special project called the quality control project and also handled to a record in research data Australia. So looking at the bottom of the screen you can see research data Australia is a data and service discovery portal provided by ANS. So we put into that an instrument description that's both hardware and software and there's a unique handle to that record. If we look at top left now at the instrument PC or client PC. Data is uploaded according to the NIF agree process so the top box above NIF agree process the user data set has to have minimal metadata as the project ID instrument ID date and time. The data was acquired implicit metadata that's in the proprietary data the native data from the instrument and conversions to one or more open data formats. The instrument operator can also upload data to the quality control project which includes the quality control standard operating procedure which of course can be updated over time and quality control data. So what this means is that when a user uploads data to the repository there's an automatic link to the quality control project and so it's possible to know the state of the instrument at the time that the data was acquired. This is what the portal looks looks like for Trudat at UWA. So we have based this on the my TARDIS platform which originated at Monash with several extensions developed during the project and we use Docker technology to be able to easily deploy different sites. So this allows easy instrument integration simple data sharing and user controlled publishing of data sets. Okay now come to the comparison of all the self assessments against the core trust seal requirements so all four sites did their own self assessments for their respective repositories. And what we can see here in this table so this shows the first eight such requirements is that essentially we independently arrived at the fairly similar level of assessment except for the cases there where we're marked in blue. And so the third one we talk about continuity of access. So Monash here believes that at this point in time that that was not assured whereas the other three sites did so I should point out this self assessment is a statement of the reality the situation at the point in time that the self assessment was completed. And then there was a difference as well at row four which is a requirement for confidentiality confidentiality and ethics Monash have this fully implemented whereas the other three sites are in various stages of getting this to be implemented. And then the other differences with the remaining requirements some differences with respect to data storage documented storage procedures. Work flows and data discovery and identification. Post funding so the project hasn't finished just because the funding has finished so we intend to maintain the services for 10 years now and we plan to meet quarterly to make sure that this happens. We are integrating additional instruments as I said we're adding micro CT instruments at the moment. We will create a project web portal so we have a single landing page for all these trusted data repository services. We're planning new national and international service deployments including one in Turku Finland. We're refining and improving the trusted data repository portal and we intend progressing the two core trust seal certification. So very quickly benefits of the NIF trusted data repository services for NIF users in the broader community means reliable durable access to data improved reliability of research outputs and provenance associated with it making NIF data more fair. Easier linkages between publications and data and stronger research partnerships. For NIF it means improved data quality improved international reputation ability to run multi center trials and for the various research institutions enhanced reputation management and means by which to comply with the draft code for responsible research and enhanced ability to engage in multi center imaging research projects. And with that I thank you and I list on the page here the various project leads at the various nodes so thank you very much.