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

Digest Attribute #2

Closed
hermann74 opened this issue Dec 16, 2022 · 1 comment
Closed

Digest Attribute #2

hermann74 opened this issue Dec 16, 2022 · 1 comment
Labels
enhancement New feature or request question Further information is requested

Comments

@hermann74
Copy link
Collaborator

hermann74 commented Dec 16, 2022

FROM Specification

RECOMMENDED. Dict. For files, this would include checksums of files. It would take the form {"<checksum-name>": "value"}

Actuellement

  • pour les entités entrantes (1 fichier par entité) : cf code
    pourquoi un dictionnaire pour plusieurs fichiers dans la spec?
  • checksum-name = "sha256"+entity[@id] , bon ?

Exemple

"prov:Entity": [
      {
        "@id": "niiri:zzX6hqo35uwZqxZOOHjk",
        "label": "my_files_sub-01_task-tonecounting_bold.nii.gz",
        "prov:atLocation": "/my_files/sub-01_task-tonecounting_bold.nii.gz",
        "digest": { "sha256_niiri:zzX6hqo35uwZqxZOOHjk": 
        "e14eaba2b2f48a040d85da4abf9a1f62e27c710c16d770ea81b4904ee160c54e"
        }

Problem:

problème d'accès au fichier (cf issue )
pour effectuer le checksum. Pour l'exemple, faux fichier texte créé avec un chemin relatif au batch.m (input)
@cmaumet

@hermann74 hermann74 added enhancement New feature or request question Further information is requested labels Dec 16, 2022
@thomasbtnfr
Copy link
Collaborator

This issue is linked to this PR : bids-standard#103. I close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants