We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We need to make use of: https://ega-archive.org/submission/programmatic_submissions/submitting-metadata For FEGA submission we need to add a key about it in the folder e.g. fega (boolean) that will classify that folder/submission as a submission to FEGA
folder
fega
Additional Info: https://ega-archive.org/submission/programmatic-submissions
introduce a new API endpoint to trigger a submission to fega
API
Integration testing, we need to mock the CEGA API
The text was updated successfully, but these errors were encountered:
This could be implemented as part of the EGA workflow, so related to #362.
Sorry, something went wrong.
i think we should not cluster too many in the workflow issue #362, as it will require adhering to https://ega-archive.org/submission/programmatic_submissions/json-message-format which would imply some mapping from our db to this format.
That makes sense.
No branches or pull requests
Description
We need to make use of: https://ega-archive.org/submission/programmatic_submissions/submitting-metadata
For FEGA submission we need to add a key about it in the
folder
e.g.fega
(boolean) that will classify that folder/submission as a submission to FEGAAdditional Info: https://ega-archive.org/submission/programmatic-submissions
DoD (Definition of Done)
introduce a new
API
endpoint to trigger a submission to fegaTesting
Integration testing, we need to mock the CEGA API
The text was updated successfully, but these errors were encountered: