Discussion: Contributors, credits, licences

[kintopp]

This data will later presumably come directly from Timbuctoo. For the sample Opele RDF we'll need to add it by hand.

[kintopp]

@marnixvb could you please discuss at Huygens how this will be stored in Timbuctoo and how it should appear here? We think that what we'll need are:

• Creator: (i.e. user who created the created the record; this might be an individual, but the record could also have been part of a bulk upload, in which case I assume it could be the name of the account associated with the upload)
• Contributors: (i.e. a comma separated list of users – sorted alphabetically? – whose changes to the record were approved; that is if A makes a change, and B approves it, then A's contribution is listed here, even if only part of the change is approved, i.e. if B revised A's original contribution).
• Core Data: (GeoNames only for now).
• Licenses: (i.e. CC-BY and CC0 for core data)

The creator and contributor names should link to their profiles in Timbuctoo. The reference gazetteer and licenses should link to webpages. See the mockup for suggested appearance.

[kintopp]

GeoNames is CC-BY v3 (or possibly v4, the site is inconsistent) and not CC0. This in turn means we don't need to distinguish between core data and extended data – both can share the same CC-BY license. Therefore:

• Creator: (i.e. user who created the created the record; this might be an individual, but the record could also have been part of a bulk upload, in which case I assume it could be the name of the account associated with the upload)
• Contributors: (i.e. a comma separated list of users – sorted alphabetically? – whose changes to the record were approved; that is if A makes a change, and B approves it, then A's contribution is listed here, even if only part of the change is approved, i.e. if B revised A's original contribution).
• License: (i.e. CC-BY with v3 or v4 to be decided)

[gklyne]

See also issue #19 (this comment: #19 (comment))