FIMDA hackathon - Githubissues

openminted / Open-Call-Discussions

A central place for participants in the open calls to ask questions

2 stars 1 forks source link

FIMDA hackathon #31

Closed Erechtheus closed 6 years ago

Erechtheus commented 6 years ago

Similar to #30 we would like to discuss how we can test the successfull integration of FIMDA docker container into the openminted test environment

galanisd commented 6 years ago

Reopened. We will close the issue when FIMDA is registered to services.openminted.eu

Erechtheus commented 6 years ago

@galanisd I added the service to services.

gkirtzou commented 6 years ago

@Erechtheus is your component private, right?

Erechtheus commented 6 years ago

@gkirtzou I updated it to public :)

gkirtzou commented 6 years ago

Perfect! One more thing, please, create the appropriate workflow so that someone could run your component using the workflow editor. For more info see https://openminted.github.io/releases/workflow-editor/

Also let me know when you have finished, so I could close the issue. If you encounter any problems, please let us know. Thanks

gkirtzou commented 6 years ago

Note that when you create an application, you wiil be asked to fill in a metadata record. Some tips for filling it in - so that they are discoverable by the users but also that users can cite you and your resource.

Give the application a unique name that humans can read and short enough
Give an explanatory description; remember you can re-use the description of the component(s) in the workflow accumulatively
Add in the inputProcessingResourceInfo the information of the first component used in the workflow (the one after omtdImpoter), and in the outputResourceInfo the information of the last component; if the annotations from previous components are retained in the final output, please add those as well
(optionally) You can use the relations set with the relation "hasPart" to document the components used in the workflow - it can be repeated multiple times.

If you encounter any problems, please let us know. Thanks

gkirtzou commented 6 years ago

Please, when you upload your component and you create an application so that a non-expert user could run it, please keep it private and send me the metadata here, so I could check them.

Also, you could add the deliverable from the tender call to your git-hub repository (if you have) and add them as documentation to the metadata of your software.

Thanks.

gkirtzou commented 6 years ago

@Erechtheus I took the initiative and create an application to test your component. In the attachement you can find the output from your component. Can you verify that is what you expect?

37873e4d-3a56-4021-b4be-bf93c573bd82.zip

gkirtzou commented 6 years ago

@Erechtheus I reran your component with another corpus that contained biological papers, and I saw fimda annotations. I consider the experiment successful. I made my application public so that non-tech users could run your component. No further things are requires. Thus I am closing the issue.

Cheers.

Previous