-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encode license and attribution information in project models #289
Comments
[Draft] Project license's mockupUsers want the ability to assign SPDX licenses or custom licenses to projects. Amended project model shape: # == Schema Information
#
# Table name: projects
#
# id :integer not null, primary key
# allow_audio_upload :boolean default(FALSE)
# allow_original_download :string
# deleted_at :datetime
# description :text
# image_content_type :string
# image_file_name :string
# image_file_size :bigint
# image_updated_at :datetime
# name :string not null
# notes :text
# urn :string
# created_at :datetime
# updated_at :datetime
# creator_id :integer not null
# deleter_id :integer
# updater_id :integer
# license :text # NEW ADDITION
#
# Indexes
#
# index_projects_on_creator_id (creator_id)
# index_projects_on_deleter_id (deleter_id)
# index_projects_on_updater_id (updater_id)
# projects_name_uidx (name) UNIQUE
#
# Foreign Keys
#
# projects_creator_id_fk (creator_id => users.id)
# projects_deleter_id_fk (deleter_id => users.id)
# projects_updater_id_fk (updater_id => users.id)
# Two new virtual fields on the project model can be emitted
The e.g. PATH {
"name": "abc123",
"license": "ADSL"
} OR PATH {
"name": "abc123",
"license": "license information lorem ipsum ..."
} To keep our list of valid SPDX identifiers up to date, when the docker container is built: we will fetch the list in JSON form from the open source spdx licenses repository Edit: In hindsight, we should probably use a polymorphic property for this. Overloading the type with freeform text and an SPDX identifier object. |
With the introduction of public permissions (#265) and other issues related to discoverability (https://github.com/QutBioacoustics/Ecoacoustics/issues/88) we need to start considering how public users of our data will use it. These concerns were raised by @JessCappadonna, @towsey, and @cofiem as well.
Thus add the following fields to projects:
A license chooser, with urls to chosen license
An attribution field (markdown enabled)
The text was updated successfully, but these errors were encountered: