de/contributorships/archivable?person_id=1 will give no Name or Explanation if config/personalize/de.yml contains a translation for the name sherpa_colors: unknown: name: "Unbekannt" explanation: "Konnte auf ..." switching to the English name, will find the proper explanation sherpa_colors: unknown: name: "Unknown" explanation: "Konnte auf ..."
Furthermore I looked at the Romeo/Sherpa Homepage and the API.
2. Language The new version http://www.sherpa.ac.uk/romeo/SHERPA%20RoMEO%20API%20V-2-9%20Addendum... allows for an optional argument language: "A new optional &la= argument allows you return data in languages other than English – currently German, Portuguese or Spanish" This might come handy with regards to i18n.
I don't see where in that document it talks about 'gray' as a color.
> 2. Language > The new version > http://www.sherpa.ac.uk/romeo/SHERPA%20RoMEO%20API%20V-2-9%20Addendum... > allows for an optional argument language: > "A new optional &la= argument allows you return data in languages > other than English > currently German, Portuguese or Spanish" > This might come handy with regards to i18n.
I assume it would be possible to add this to the call when Bibapp calls to get Sherpa data, but I'm not sure that it actually uses anything that comes back except for the romeocolour. If we find someplace that is does then I can look into it, but if not then I'm just as happy to key off of the English color and provide translations.
"<romeocolour> This field gives the colour-code assigned by RoMEO to the publisher. Possible values are: green, blue, yellow, white, and gray. See http://www.sherpa.ac.uk/romeoinfo.html#colours for an explanation of the RoMEO colours. gray is used for publishers found in DOAJ that have not yet been analysed by RoMEO."
With regards to the new language attribute, you're right as long as we use only the color we won't need it. Just found it interesting if ever anything more is wanted like the policies etc.
>> Wonder whether this should be included in BibApp in general.
> I don't see where in that document it talks about 'gray' as a color.
>> 2. Language >> The new version >> http://www.sherpa.ac.uk/romeo/SHERPA%20RoMEO%20API%20V-2-9%20Addendum... >> allows for an optional argument language: >> "A new optional &la= argument allows you return data in languages >> other than English >> currently German, Portuguese or Spanish" >> This might come handy with regards to i18n.
> I assume it would be possible to add this to the call when Bibapp calls > to get Sherpa data, but I'm not sure that it actually uses anything that > comes back except for the romeocolour. If we find someplace that is does > then I can look into it, but if not then I'm just as happy to key off of > the English color and provide translations.
