search

hpde / SMWG

SPASE resource descriptions with SPASE Metadata Working Group naming authority.
8 stars 5 forks source link

About French ground facilities naming. #3

Closed BaptisteCecconi closed 4 years ago

BaptisteCecconi commented 5 years ago

I'm trying to prepare a future series of resource inputs into the SPASE registry, and I just reviewed the French ground facility resources linked to Observatoire de Paris:

Observatory Tree

I spotted those 3 entries:

Note that the official name the ObsParis is Observatoire de Paris, although its DNS is obspm.fr. ObsParis is a single entity including the Paris and Meudon physical sites.

Instrument Tree

I spotted those 3 entries:

These instruments should be listed in the SPASE registry. In the local LESIA documentation, there is no difference between the spase://SMWG/Instrument/Meudon/Spectroheliograph and spase://SMWG/Instrument/OBSPM/OBSPM instrument and they are referred to as Spectroheliograph. So that I propose to reorganize the tree this way:

We may want to keep the Meudon name in the SPASE hierarchy, so we could have spase://SMWG/Instrument/ObsParis/Meudon/Spectroheliograph instead.

I need to add 3 new entries in the ObsNancay tree:

NB: I will update the issue later, as the spase-group.org website looks down for now

BaptisteCecconi commented 5 years ago

Here is the new proposed scheme for SWMG/Observatory:

Here is the new proposed scheme for SWMG/Instrument:

Here is the new proposed scheme for SWMG/Repository:

I will submit those changes internally for review and comments and then issue the pull request.

J-Christophe commented 5 years ago

Hello Baptiste,

I suggest that we use existing identifiers for observatories provided by IAU : https://en.wikipedia.org/wiki/List_of_observatory_codes. This is an interoperability issue. If you we use something already standardized, softwares could easily attach some information (e: longitude, latitude, latitude of the observatory) coming from somewhere to our data without creating a mapping file (which is not interoperable)

In addition, this observatory code seems to be used in other softwares : http://dc.zah.uni-heidelberg.de/obscode/q/query/form

If one code is missing, we could provide an input to IAU. If it takes too much time, we could add a kind of name space to define the authority (IAU, you, me, SPACE).

So for Meudon, we could have spase://SMWG/Observatory/IAU:OBS:005. For Nançay, which is not is the list, we will get space://SMWG/Observatory/SPACE:OBS:Nancay

Jean-Christophe

BaptisteCecconi commented 5 years ago

Hi Jean-Christophe,

two remarks:

By the way, the alternateID could also be used in other resource descriptors, such as the Person tree, with ORCIDs.

Baptiste

Le 27 oct. 2018 à 12:40, Jean-Christophe Malapert notifications@github.com a écrit :

Hello Baptiste,

I suggest that we use existing identifiers for observatories provided by IAU : https://en.wikipedia.org/wiki/List_of_observatory_codes. This is an interoperability issue. If you we use something already standardized, softwares could easily attach some information (e: longitude, latitude, latitude of the observatory) coming from somewhere to our data without creating a mapping file (which is not interoperable)

In addition, this observatory code seems to be used in other softwares : http://dc.zah.uni-heidelberg.de/obscode/q/query/form

If one code is missing, we could provide an input to IAU. If it takes too much time, we could add a kind of name space to define the authority (IAU, you, me, SPACE).

So for Meudon, we could have spase://SMWG/Observatory/IAU:OBS:005. For Nançay, which is not is the list, we will get space://SMWG/Observatory/SPACE:OBS:Nancay

Jean-Christophe

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.