Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make quality reports available on disk #149

Open
gothub opened this issue Aug 3, 2018 · 0 comments
Open

Make quality reports available on disk #149

gothub opened this issue Aug 3, 2018 · 0 comments
Assignees
Labels
metadig All issues related to metadig

Comments

@gothub
Copy link
Contributor

gothub commented Aug 3, 2018

It was mentioned at the weekly development meeting that the quality reports that the metadig engine creates should be made available on disk, in a manner similar to how metacat stores files on disk. Other services can then have bulk access to these reports for further processing, aggregation and any other kind of analysis.

If the reports are made available in this manner, would it be necessary to include metadata in the file and directory names to assist in locating the desired file? For example, we might have

/mnt/glusterfs/metadig-engine/reports/knb.suite.1/doi:10.6085_AA_CMRX00_XXXITBDXLSR01_20030717.50.5.json

In his case, the pid would have to be changed so that the filename is legal (on Ubuntu).

Would any other info need to be stored in the directory or filename, or would they all be stored in a single directory and any metadata would be made available via a database or some other mechanism?

What format types would have to be generated and stored as well, i.e. (XML)?

Would this disk store be made available via nfs? As these would be stored via glusterfs on the k8s
cluster, they could also be made available via gluster over a network connection.

Thoughts @mbjones @csjx ?

@gothub gothub added the metadig All issues related to metadig label Aug 3, 2018
@gothub gothub added this to the 2.1.0 milestone Aug 3, 2018
@gothub gothub self-assigned this Aug 3, 2018
@gothub gothub modified the milestones: 2.1.0, 3.0 Apr 2, 2020
@jeanetteclark jeanetteclark removed this from the 3.0 milestone Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
metadig All issues related to metadig
Projects
None yet
Development

No branches or pull requests

2 participants