Wikidata:Property proposal/SHERPA/RoMEO publisher ID
SHERPA/RoMEO publisher ID[edit]
Originally proposed at Wikidata:Property proposal/Organization
Description | identifier of an academic publisher in the SHERPA/RoMEO database of archiving policies |
---|---|
Represents | SHERPA/RoMEO (Q16172543) |
Data type | External identifier |
Domain | publisher (Q2085381) |
Allowed values | [1-9]\d* |
Example 1 | Geological Society of America (Q1503216) → 105 |
Example 2 | Grodno State Medical University (Q2067552) → 2578 |
Example 3 | Guilford Press (Q5615936) → 371 |
Example 4 | Harvard University Press (Q1587900) → 3243 |
Source | http://www.sherpa.ac.uk/downloads/ |
Mix'n'match | 1190 |
Number of IDs in source | 2517 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | http://www.sherpa.ac.uk/romeo/pub/$1/ |
See also | Sherpa Juliet ID (P4636) |
Motivation[edit]
Note that SHERPA/RoMEO is primarily a database of self-archiving policies, not of publishers, because some publishers (such as the first example) can have multiple policies, hence multiple records in SHERPA. In this case they still have a designated "default" policy, so I think we can use that. If we want to create items for self-archiving policies we could also use the ids on such items.
Notified participants of WikiProject Open Access. − Pintoch (talk) 03:41, 20 February 2019 (UTC)
Discussion[edit]
Comment Sherpa Romeo is listed as a third-party formatter URL (P3303) for ISSN (P236) but that is for linking to journal open access policies. We already have Sherpa Juliet ID (P4636) property for the sister site containing details of research funder policies. Simon Cobb (User:Sic19 ; talk page) 07:01, 20 February 2019 (UTC)
- Support This property will let us connect Wikidata to the publisher open access policies in SHERPA/RoMEO that cannot be linked with the ISSN formatter URL. Simon Cobb (User:Sic19 ; talk page) 07:01, 20 February 2019 (UTC)
- Looking up journals by ISSN is indeed the right thing to do. For me the main advantage of this property would be mostly to import the journal-publisher relationships (the scholarly communications industry does not seem to agree on identifiers for publishers yet). − Pintoch (talk) 07:27, 20 February 2019 (UTC)
- Support David (talk) 07:18, 20 February 2019 (UTC)
- Support. Nomen ad hoc (talk) 12:09, 20 February 2019 (UTC).
- Support. --Jaireeodell (talk) 13:24, 20 February 2019 (UTC) I agree that it would be useful for associating journals with publishers and journals with self-archiving policy types.
- Support external identifier. 18:14, 20 February 2019 (UTC)
- Support. Oa01 (talk) 12:44, 21 February 2019 (UTC)
- Support --Ptolusque (.-- .. -.- ..) 12:45, 21 February 2019 (UTC)
- Support. We should perhaps also consider the other SHERPA service databases. [1] In light of Plan S, SHERPA FACT is going to get a lot more important soon. HLHJ (talk) 03:54, 23 February 2019 (UTC)
- Support Jneubert (talk) 17:55, 27 February 2019 (UTC)
- Support. YULdigitalpreservation (talk) 13:00, 28 February 2019 (UTC)
- Support Megs (talk) 21:33, 2 March 2019 (UTC)
- Support Dan scott (talk) 21:02, 6 March 2019 (UTC)
OK @Pintoch, Sic19, ديفيد عادل وهبة خليل 2, Nomen ad hoc, Jaireeodell, Oa01: done. --Kolja21 (talk) 22:35, 26 March 2019 (UTC)