-
Notifications
You must be signed in to change notification settings - Fork 3
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
Send data to APICURON (placeholder issue) #1013
Comments
Yes we will speak with them again at some point soon -ish. MAybe OCt/Nov ish. Let's get other stuff out of the way first. |
Turns out there was a bug that they've helped me work around. |
I've changed the nightly Chado processing code to make a file for testing the APICURON API. After a few false starts I've been able to submit the file to the dev APICURON server. The test file contains a record for each time a user has managed to get a publication/session approved. Each record looks like: {
"activity_term": "publication_curated",
"timestamp": "2022-02-24T11:54:36.000Z",
"curator_orcid": "0000-0003-4148-4606",
"entity_uri": "https://www.pombase.org/reference/PMID:15964794"
} Let's talk about this on Zoom/Skype. I'd like to see what happens when you try to log in to the dev server. Note to self, example of how to post Curl using: curl -X 'POST' \
'https://dev.apicuron.org/api/reports/bulk' \
-H 'accept: */*' \
-H 'version: 2' \
-H 'authorization: bearer ...' \
-H 'Content-Type: multipart/form-data' \
-F 'delete_all=pombase' \
-F 'reports=@apicuron_data.json;type=application/json' |
Current status (2023-10-09): I've reported a few bugs via the APICURON Slack (on 2023-10-5) and I'm waiting for replies. |
Those bugs are fixed. |
As an experiment, I've added a command at the very end of the nightly load script to attempt to send our latest data to APICURON. I've put it at the end of the script so that if there are any problems it won't cause other load steps to be missed. I'll check on Wednesday to see if that works OK. Note that the data is still very minimal: just records of which ORCID curated which paper. Val, when you have time (maybe next week?) we should try to get you logged in on the dev APICURON server to see how it looks to you. |
Yes, let's do this next week. |
The load script fell over just before trying to upload to APICURON because I made a typo implementing #886. It's fixed now and I'll check the APICURON upload on Thursday morning. |
That's working now so the PomBase data in the dev APICURON is now updated nightly. |
I've added a second APICURON "Activity Term" for when a user submits a HTP dataset. I want to see how it looks in the interface if a user has two different types of record. I've changed the code the generates the JSON too. The new term ID is "provided_dataset". The existing term ID is "publication_curated". These are just terms for testing on the dev server. When we move other to the main apicuron.org we can rename or replace them. |
From the call last week:
(Edit) See also: |
Store in ReferenceDetails and write to APICURON JSON file. Refs pombase/pombase-chado#1013
The approver records are now sent to the dev APICURON too. We now have three "activity terms":
I think that's quite a good set for this project. |
Add new "Importer" Moose Role with code for recording the annotation_file_curator pubprop. Refs #1013
I don't think we have an issue specifically for this: we need to send curation data to APICURON.
While implementing pombase/website#525, I wrote the code to collect the basic curation stats for the annotation from Canto. So that's a start.
We now need to:
We need to add more detail to that list. :-)
The text was updated successfully, but these errors were encountered: