Clarify licence information, detection status and free-to-read

CottageLabs / LanternPM

Lantern meta repository for product management

1 stars 0 forks source link

Clarify licence information, detection status and free-to-read #109

Open richard-jones opened 8 years ago

richard-jones commented 8 years ago

We need to represent licences in an easier to use way via the API. Recommend:

Getting rid of "non-standard-licence" as a string that can appear in the licence field
Putting "free-to-read" in another field, which would be a boolean

Then for Wellcome we'd just translate any licence which is one of their non-standard ones to the string "non-standard-licence" in the CSV.

richard-jones commented 8 years ago

Might be worth a chat about how exactly we do this one. The desire to separate free-to-read from the licence has been long coming, and with the distinction that Monitor makes between these two things, it is probably the time now to do it.

Making this change may change the API, so I need to keep in the loop since any changes to the API now could break the Monitor integration, which currently has a workaround in place for this field.

markmacgillivray commented 8 years ago

Yeah we better discuss this one

emanuil-tolev commented 8 years ago

Getting rid of "non-standard-licence" as a string that can appear in the licence field

We actually do this in the wellcome format function now, it's one of the last changes I made the week before. It does mean we can remove non-standard-licence as a type string from the licence sheet. But yes, best discussed.