OpenEnergyPlatform / OpenEnergyPlatform/organisation

FAIRsharing query - new record for OEP database

Open
#49 2 comments 1 reaction 1 assignee View on GitHub

@Ludee is already working on this.

Since Mar 30, 2022.

documentation SIROP
Dominant language
CSS
Stars
10
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Dear OEP Team,

I’m contacting you on behalf of FAIRsharing[1], the online registry of scientific data standards, databases and policies. Our aim is to make your resource as visible as possible to as large an audience as possible.

We have a FAIRsharing record for your resource[2]. To ensure our information is as correct and up to date as possible, would you or someone from your team quickly scan the record[2] and ‘claim’ it? (To claim, see link [3] below.)

Claiming a record as either a group or an individual gives you the opportunity to make changes to the record yourself, allowing you complete control over how your resource is displayed in FAIRsharing. Maintainers are also notified if our curation team edits the record, if users ask questions, or if the record is linked from another record, such as from a journal publisher data policy. In addition, if you claim a record(s) as an individual, you can link the record to your ORCID.

FAIRsharing is about making your resource discoverable to a variety of users, such as journals and publishers, researchers and service providers, research and infrastructure projects and programmes, as well as curators, librarians, funders and other policy makers and data scientists[4]. A contact is essential should they have any questions about your resource.

Thank you and best wishes,
Allyson

[1] https://fairsharing.org
[2] https://fairsharing.org/3968
[3] For details on creating an account with us and claiming your record, please visit https://fairsharing.gitbook.io/fairsharing/
[4] https://fairsharing.org/communities

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.