Correspondence Tables - reproducibility objectives

[bkuczenski]

Review the proposed work around Correspondence Tables and EXIOBASE and brainstorm about specific reproducibility objectives.

You can do work right here in the comment / discussion area for the issue, or commit code/documents to the repository.

[mfastudillo]

I had a very quick look to some of the tables, I think they need some cleaning and more standard format (e.g. first row the header). Some of the things that come to mind

• tables should be in csv format (they are so far)
• do scripted data processing to clean them and create metadata.
• I suggest we create descriptors using frictionless data package. To my understanding that would make things easier. we may want to add fields such as version, contact information and license.

[mfastudillo]

It occurs to me that we should be able to apply the FAIR principles to exiobase and that should facilitate the expression of the database in RDF... We could script something to transform the data as downloaded from the website, into something that can be more "readily digested" by our tools. Does it make sense? Which working group would be working with this?

To be Findable:

• [ ] F1. (meta)data are assigned a globally unique and persistent identifier
• [ ] F2. data are described with rich metadata (defined by R1 below)
• [ ] F3. metadata clearly and explicitly include the identifier of the data it describes
• [ ] F4. (meta)data are registered or indexed in a searchable resource To be Accessible:
• [ ] 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 are accessible, even when the data are no longer available To be Interoperable:
• [ ] I1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.
• [ ] I2. (meta)data use vocabularies that follow FAIR principles
• [ ] I3. (meta)data include qualified references to other (meta)data To be Reusable:
• [ ] R1. meta(data) are richly described with a plurality of accurate and relevant attributes
• [ ] R1.1. (meta)data are released with a clear and accessible data usage license
• [ ] R1.2. (meta)data are associated with detailed provenance
• [ ] R1.3. (meta)data meet domain-relevant community standards

[cdgaete]

Hi Miguel,

I am also in this group, actually, I know how to code with python, but I am not a software developer, so I am not familiar with this stuff (reproducibility), and unfortunately, two weeks ago I received reviews from journals of two papers I submitted some time ago, therefore, I did not have much time to study about reproducibility. I have read your post, and it makes a lot of sense, so please if you have a much clear idea, share it with me tomorrow so we can start hands on the project. As I am more familiar with Entso-e I am working on that now.

[bkuczenski]

Miguel, I think it would be our group that would be in charge of attaining FAIR standards :) This strikes me as another "during hackathon" issue! #8