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

AIND Bucket Indexer should also update individual metadata files in S3 #55

Closed
10 tasks done
helen-m-lin opened this issue May 20, 2024 · 1 comment · Fixed by #57
Closed
10 tasks done

AIND Bucket Indexer should also update individual metadata files in S3 #55

helen-m-lin opened this issue May 20, 2024 · 1 comment · Fixed by #57
Assignees

Comments

@helen-m-lin
Copy link
Collaborator

helen-m-lin commented May 20, 2024

User story

As a user, I want to see changes updated in the core schema files in S3 after updating a metadata record in DocDB, so changes are synced in s3 and docdb.

Currently, the aind_buckets_indexer.py job will check for updates to records in DocDB and update the metadata.nd.json files in S3.
We also want the individual metadata JSONs (subject, rig, etc) updated in the S3 buckets.

Acceptance criteria

  • Given the populate_s3_with_metadata_files.py job is run, then the core fields from the metadata.nd.json get saved to json files.
  • Given the populate_s3_with_metadata_files.py job is run and there already is a {core_schema}.json, the original contents are copied to another file as {core_schema}.old.json.
  • Given the aind_bucket_indexer.py job is run and there were updates to a metadata record in docdb, the core schema jsons get updated in S3 as well.
  • Given the aind_bucket_indexer.py job is run and a metadata.nd.json is found or created in S3, also ensure core jsons are copied and in sync.

Sprint Ready Checklist

  • 1. Acceptance criteria defined
  • 2. Team understands acceptance criteria
  • 3. Team has defined solution / steps to satisfy acceptance criteria
  • 4. Acceptance criteria is verifiable / testable
  • 5. External / 3rd Party dependencies identified
  • 6. Ticket is prioritized and sized

Notes

Add any helpful notes here.

@helen-m-lin helen-m-lin self-assigned this May 20, 2024
@helen-m-lin
Copy link
Collaborator Author

Discussed with @dyf and @saskiad, we can write the original core schema jsons to:
s3://{bucket}/{s3_prefix}/original_metadata/{core_schema}.{date_stamp}.json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant