-
Notifications
You must be signed in to change notification settings - Fork 13
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
NF: NIDMResults metadata extractor draft #41
Conversation
Codecov Report
@@ Coverage Diff @@
## master #41 +/- ##
==========================================
- Coverage 89.03% 88.38% -0.65%
==========================================
Files 19 21 +2
Lines 930 999 +69
==========================================
+ Hits 828 883 +55
- Misses 102 116 +14
Continue to review full report at Codecov.
|
Here is a minimal JSON file we can use for testing: https://raw.githubusercontent.com/cmaumet/nidmresults-spm/export_from_json/test/spmexport/ex_spm_full_example001/nidm_minimal.json |
Q @cmaumet: The metadata contains absolute paths, e.g.:
Do they have to be like this, or could they be relative to the "root" of the result structure? In the present form it is hard to locate the file in the ZIP once extracted to an arbitrary location. |
Not that the tests are currently broken, because of datalad/datalad#2756
Replaced by psychoinformatics-de/datalad-hirni#102 |
Quick draft of a NIDM result metadata extractor. This is using a JSON-LD representation as input that is not very suitable for the search implementations we have.