Proposal.001: GRS LinkOut Implementation

From Genomic Standards Consortium

[edit] Deadline for contributions to proposal

28th March 2008 4pm GMT

Please edit this document up to the deadline stated. Further to this date, a vote will be taken on the options stated

[edit] Background

It is proposed that the Genomic Rosetta Stone identifier mapping is hosted by NCBI LinkOut.

On 19th March 2008, the LinkOut team agreed to host the identifier mapping resource files : Genomic_Rosetta_Stone_and_LinkOut

Several ideas have been suggested as to how to organise the identifier mapping files and submission to NCBI LinkOut.

We need to reach consensus on the approach to take, before we can submit files to NCBI LinkOut.

[edit] Proposal

[edit] Option 1

members of the GRS provide one identity file and one resource file to the INSDC.

This would take less communication between GRS and NCBI, but all synchronisation must be orchestrated by the GRS. Also, this would only require the GRS to register with the NCBI, without the need for the individual partners to register.

[edit] Option 2

GRS provides one identity file and members of the GRS each provide their own resource file to the NCBI.

Each member may determine its own pace of updating information with the NCBI. Don't know if this scenario is technical possible within the Linkout system. Again, this would only require the GRS to register with the NCBI, without the need for the individual partners to register.

[edit] Option 3

Each GRS member provides its own identity and resource file to the NCBI.

All members need to register, and may determine their own pace of updating information with the NCBI. In this scenario, the GRS does not even intervene in the communiction with the NCBI.

One reason to choose this option is that there are potential applications of the resource data to be held in LinkOut beyond the GRS application. End users maybe want to consume the data in ways that we have not yet identified. As such, it is preferable not to put the data from all the data providers in a delimited GRS set that might not fit other applications.

[edit] Discussion

From Lynn Schriml 27th March 2008:

Looking at the proposals, I don't think that the second proposal is technically possible within linkout.

One comment for the third option is that having each member register separately, would allow the individual groups to update files independently and would also greatly decrease the overhead of coordination of project data on the GRS side of things. Option 1 would require quite a lot of project management time, in the long term, I think. But would provide a unified picture that all of these different sources are GRS data.

Can LinkOut provide that umbrella for GRS. Given the individual projects, can each have it's own Linkout, and also be put under the GRS umbrella linkout as well ? That the individual projects are GRS members?

Cheers,

Lynn