A link to the EPOS ICS Portal, which is still under development, is available here, http://nodedev.bgs.ac.uk/epos/epos-gui/master/ Please note that this site is under development and there are many unfinished components. The development team hope that users will provide feedback which can be used to inform the final design.
About this board
You can use this board to submit questions that you consider relevant for everybody.
How will the EPOS user interface work?
Where can I access EPOS use cases?
EPOS use cases are available in the 'Requirements & Use Cases (RUC) collection' level-2 documents that were collected from the TCSs at the start of 2016.
Can the work of WP7 be clarified?
WP7 is in charge of developing the Integrated Core Services (ICS). The ICS is the place where the integration of Data, Data Products, Services and Software (DDSS) from the TCS is achieved. The communication between TCS services, which make DDSS available, and ICS will be achieved by means of connectors (e.g. web services). Such connectors are developed in a collaborative way by TCS and ICS staff.
In addition, WP7 will provide guidelines and support to TCS who need help with developments.
Will services be available only through EPOS ICS? Or also through other portals/websites etc?
No, TCS services do not need to be provided solely to EPOS. The services that the TCSs provide to EPOS can also be made available to other portals/websites. However, aspects such as rights, security, privacy must be respected. For further details on how EPOS will access services, please see the Guidelines Document ICS-TCS-integration-guidelines-level-2 (available here: https://intranet.epos-ip.org/file/400/download?token=83CtdU2q)
How will new services be added to EPOS during the Operational Phase?
Technically, in the same way they are made available in the Implementation Phase. However the ERIC will have a clear governance and rules to define which services will be included in the EPOS-ICS in the future.
How will software be integrated into EPOS (should a generic component developed at TCS level be deployed in the ICS-C or TCS layer)? How should software be managed and maintained in the long term??
There is a need to define what “software” means. Standalone desktop software packages or source code will be dealt with as Digital Objects. It means they’ll have to be described by means of appropriate metadata.
Other kind of software (e.g. visualization software) can be included within TCS if they are made available by means of APIs or web services. There is always the need for an interface so that the software can be “plugged” into ICS. This document provides some additional information: Guidelines Document ICS-TCS-integration-guidelines-level-2 (available here: https://intranet.epos-ip.org/file/400/download?token=83CtdU2q)
What level of metadata at ICS-C level is required for each service?
For more information, please see the EPOS metadata model reference document available at https://docs.google.com/document/d/1awBBniKlyGA_F7H386WIbPMgmreXSyd8NFd_eaHklOc/edit?pref=2&pli=1
Who will undertake the metadata mapping? Is this the job of the TCS or the ICS?
It is a collaborative work. TCS staff have the knowledge of their data (datasets, software and services) and know the main information to do the mapping (e.g. the meaning of metadata terms, which are the most relevant metadata elements to describe the data, etc.). ICS staff has the knowledge about CERIF and will facilitate the mapping process.
Do TCS need to use CERIF as the metadata standard? Why not adopt INSPIRE compliant standards instead?
TCS are not bound to use CERIF as their metadata model. They can do it if they wish (and there are advantages both for the TCS and for interoperability in doing so), but they don’t have to. They can use other metadata models to describe their DDSS - in which case conversion to/from CERIF has to be developed using TCS effort as well as ICS input.
TCS communities are all invited to use metadata standards which are INSPIRE compliant, well described or at least accepted by a huge community (de facto standards). ICS staff will provide guidelines about it.
I am concerned that our TCS specific metadata structure cannot be mapped properly into CERIF because I don’t see the relevant entities. How do you plan to convert TCS-specific metadata to CERIF?
The WP7 metadata group is providing an EPOS baseline to which TCS metadata will be easily mapped. This baseline represents all the main elements for which a TCS should provide metadata. The process of mapping TCS metadata to this EPOS baseline is a collaborative task which requires both TCS scientist, technical staff and ICS staff to work together in order to define: a) most relevant metadata element from TCS DDSS to be mapped, b) terms, ontologies, vocabularies from the specific community.