| Service overview | |
|---|
| Service name | Open Information Linking for Environmental science research infrastructures (OIL-E) |
|---|
| Service area | data |
|---|
| Service phase | discovery |
|---|
| Service description | OIL-E is a developing framework for addressing the semantic linking requirements of environmental science e-RIs. Specifically, it is intended to provide a machine-readable bridge between the ENVRI Reference Model and other concept models related to research infrastructure, architecture and scientific (meta)data. |
|---|
Customer group | RI data engineers/architects |
|---|
| User group | Data-driven researchers |
|---|
| Value | OIL-E is intended to provide technical and methodological guidance for the linking of different controlled vocabularies in order to help the construction of cross-cutting services. |
|---|
| Tagline | Open linking between environmental science RI reference modelling and controlled vocabularies. |
|---|
| Features | List of distinct characteristics for this service |
|---|
| Service options | | Option | Name | Description | Attributes | |
|---|
| 1 | Add a name for this option | Add a description for this option; this description is targeted to potential customers who need to understand what each option is about and being able to choose the best for their needs | Add attributes as numbered bullet lists in the form of 1. attribute name: [possible values] 2. attribute name: [possible values] ... | | | 2 | | | | | | 3 | | | | |
|
|---|
| Access policies | Wide access |
|---|
| Service management information | |
|---|
| Service owner * | Paul Martin |
|---|
| Contact (internal) * | p.w.martin@uva.nl |
|---|
| Contact (public) | External contact (e.g., e-mail, phone) to ask information about the service |
|---|
| Request workflow * | Description of the workflow that a customer needs to follow to request the service |
|---|
| Service request list | List of requests that a user can submit to the service desk during the provision of the service |
|---|
| Terms of use | URL to a document containing the rules which one must agree to abide by in order to use the service |
|---|
| SLA(s) | Link to URL to a document containing information about the levels of performance that a service provider is expected to achieve (service level agreement) |
|---|
| Other agreements | List of agreement documents that are associated to this services (e.g. OLA, UA) |
|---|
| Support unit | Name of the support unit in the EGI Helpdesk |
|---|
| User manual | URL to the user manual for this service |
|---|
| Service architecture | |
|---|
| Service components | List of service components that are the minimum required to make the service available and their TRL | # | Type | Name | Description | TRL [1] |
|---|
| 1 | Choose: Enabling or Enhancing Definitions: - Enabling service components are the minimum set of service components that make the service available - Enhancing service components are any additional service components that improves the service, however, the service would still run without them, even if at lesser quality. | Name of the component | | | | 2 | | | | |
|
|---|
| Finances & resources | |
|---|
| Payment model(s) | Supported payment models and restrictions that apply to each of them; example of types of payment models are: free, pay-as-you-go, subscription, membership to corporate customers , higher education, etc. |
|---|
| Pricing | Describe the price scheme for this service in case the customer is charged for access/usage |
|---|
| Cost * | The costs required to develop (CAPEX) and maintain/operate (OPEX) the service in the best case, e.g. human effort; financial investment |
|---|
| Revenue stream(s) * | e.g. public funding, membership fees, in-kind, paid (specify price) |
|---|
| Action required | List the actions that are required to complete the service portfolio entry according to the specific service phase; if no actions are required, write 'no' |
|---|