-
Notifications
You must be signed in to change notification settings - Fork 2
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
50 clowder20 submit file to extractor #51
Conversation
at different points in the code, the version will be checked different methods will use different endpoints and will use the bearer token instead of the key
problem - the method in the extractor is not getting the secret key possible fix - use token for secret key
need to add extractor info
more to be added later for datasets once that completed in clowderv2
…o make sure future metadata that matches is not reprocessed)
some routes not implemented in v2 clowder, left for later
This clowder2 pull request is also reliant on this one: |
Ran this with Clowder v1 develop and wordcount worked! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with clowder v1 and v2 both.
For testing, if you are testing with clowder v2, here is the entry for extractor 'wordcount' you can add to listeners. if you run clowder2 and have wordcount running at the same time, it will submit and post metadata back, which should now be visible on main.
|
used in filedigest
upload file for v2 did not properly return the id of the uploaded file. added a text file (looks like the original was not checked in) gave it a more descriptive name.
files.get_summary gets the equivalent of the file info in v2
should fix build errors
…ctor 287 clowder2 test extractor
These changes will allow a file to be submitted to an extractor and the metadata will post. I have not yet handled cases where new files are uploaded or tags. Easiest way to test is to use the wordcount extractor.
With this branch, add .env file to the pyclowder directory and put in
clowder_version=2.0
Right now I am sending in the Bearer Token from clowder2.0, and then using the Bearer Token in place of the extractor-key or secretKey. I am not sure that this will be a good strategy long term. If an extractor takes a long time to complete, the token may expire, but this seemed like a good enough approach for now.
The branch this works with for clowder2.0 is
https://github.com/clowder-framework/clowder2/tree/register-extractor-submit-file