Merge !148 is great
As we are now building from local source, do we still need to apt install git
?
https://gitlab.in2p3.fr/escape2020/wp3/eossr/-/blob/master/Dockerfile#L5
Was this closed because it has already been solved, or is the solution is being worked on elsewhere ?
ESAP are working on a metadata schema that would compliment the current codemeta by describing the executable components associated with an OSSR record.
Initial outline for the metadata is on these wiki pages:
Work in progress to apply this to some of our use cases:
ESAP are working on a metadata schema that would compliment the current codemeta by describing the executable components associated with an OSSR record.
Initial outline for the metadata is on these wiki pages:
Work in progress to apply this to some of our use cases:
ESAP are working on a metadata schema that would compliment the current codemeta by describing the executable components associated with an OSSR record.
Initial outline for the metadata is on these wiki pages:
Work in progress to apply this to some of our use cases:
The example codemeta file references the funding agency using a DOI identifier.
"funder":[
{
"@type": "Organization",
"name": "ESCAPE: European Science Cluster of Astronomy & Particle physics ESFRI research infrastructures",
"funder": {
"@type": "Organization",
"@id": "https://doi.org/10.13039/501100000780",
"name": "European Commission"
}
}
],
Is there a howto guide that explains how to find the DOI for a funder ?
Using a process of reverse engineering from the DOI in the example I found the registry of well known funding sources .
I couldn't find an easy way to search the registry, so I ended up going to their GitLab repository and doing a text search of the RDF file for the name of my funder.
Yay for OpenSource, but I'm sure there must be a better way of doing this ?
@vuillaume thanks for looking into this. Can we add some of this to the OSSR documentation to help others find their funder DOI when they are writing their codemeta files.
Having read the page, we don't need the s, OSSR-container-image-policy would work fine.
Discussion should continue on this eOSSR wiki-page.
Unfortunately, URLs with apostrophes in them don't survive well in emails. For accessibility, could we rename the page ?
Is this the correct keyword for this ? https://gitlab.in2p3.fr/escape2020/wp3/eossr/-/blob/master/codemeta.json#L40
"keywords": ["jupyter-notebook"],
The software is a Python library not a Jupyter notebook.
This statement in the Dockerfile https://gitlab.in2p3.fr/escape2020/wp3/eossr/-/blob/master/Docker/Dockerfile#L5
RUN pip install https://gitlab.in2p3.fr/escape2020/wp3/eossr/-/archive/master/eossr-master.tar
This means that a developer cannot modify the code and create a Docker image from the local copy. The Docker build will always ignore the content of the local copy and use whatever is in the tar file stored in the gitlab archive.
This also means that trying to build a container for a specific version by checking out a tagged version of the git repository will not work. The Docker build will always revert to whatever is in the tar file stored in the gitlab archive.
The only way to create a Docker container with modified code using this Dockerfile is to compile the code, package it as a tar file, upload it to the gitlab archive and label it as the current latest live version. However, doing so would mean that anyone else who tried to build a container using this Dockerfile would also get the modified version.
The Dockerfile should be placed at the root of the project and it should install the library from the local source code, or the project should provide a shell script that tells docker build
to use different locations for the Dockerfile and build context.
The human-readable install instructions says:
You can also run it with docker:
docker run -it gitlab-registry.in2p3.fr/escape2020/wp3/eossr:latest
The machine-readable metadata is missing an equivalent section that describe how to discover, access and run the container image.
These look hopeful, could we adopt this syntax ?
Dave Morris (d95f7921) at 15 Sep 17:42
The ESCAPE template project contains two container images, one for docker and one for singularity. https://zenodo.org/record/4923992
The AMIGA-IAA/hcg-16 use case contains three container images, each containing different software. https://github.com/AMIGA-IAA/hcg-16/tree/master/docker
ESAP needs to be able to show the user what containers are available, and it needs to know what services are able to run them.
For reference, we may want to add this project to OSSR in the future. https://github.com/ivoa/lyonetia
Over the history of the project it has received funding from 5 grants from 3 funding sources. https://github.com/ivoa/lyonetia#project-funding
The example codemeta file references the funder
agency and funding
grant.
"funder":[
{
"@type": "Organization",
"name": "ESCAPE: European Science Cluster of Astronomy & Particle physics ESFRI research infrastructures",
"funder": {
"@type": "Organization",
"@id": "https://doi.org/10.13039/501100000780",
"name": "European Commission"
}
}
],
"funding": "824064"
As a new joiner using the example I have questions:
Is the nested structure of funder
Organization", inside funder
Organization", correct ?
Is ESCAPE a funding source in it's own right, or is it a project funded by the European Commission ?
Is there any guidance on how to put something like this together ?
The example codemeta file references the funding agency using a DOI identifier.
"funder":[
{
"@type": "Organization",
"name": "ESCAPE: European Science Cluster of Astronomy & Particle physics ESFRI research infrastructures",
"funder": {
"@type": "Organization",
"@id": "https://doi.org/10.13039/501100000780",
"name": "European Commission"
}
}
],
Is there a howto guide that explains how to find the DOI for a funder ?
Using a process of reverse engineering from the DOI in the example I found the registry of well known funding sources .
I couldn't find an easy way to search the registry, so I ended up going to their GitLab repository and doing a text search of the RDF file for the name of my funder.
Yay for OpenSource, but I'm sure there must be a better way of doing this ?
For reference, this issue was logged against the template_project_escape project because it claimed to be the example template that everyone should follow.
This is just a reminder that when this issue is resolved, the example project needs to be updated to follow the new guidelines.
One GitHub repository may have multiple containers associated with it.
In some cases they may be different packaging of the same software e.g. docker and singularity containers for the same software.
In some cases they may be different software in each container, e.g. command line client and server deployment for a service.