Public accessing the Park Name dataset in BC Data Catalogue

[kgorana]

Description

The purpose of this ticket is to (in order):

1. have the park name dataset published on BCDC now that the approvals, records, etc steps are all done
2. ensure that the public is easily and successfully able to access this dataset on BCDC

Context:

• We want that the public has quick and easy access to the names of BC Parks from a trusted source - which is coming from the ministry directly, supporting the transparency, accessibility, and compliance aspects of BC Gov's digital principles.
• This data can be used to make informed decisions and create opportunities for the benefit of all British Columbians.
• The BC Data Catalogue provides the easiest access to government's data holdings, as well as applications and web services. Park Name dataset, under the Open Government License - British Columbia #123, will be made discoverable in the Catalogue.
• Catalogue users can subscribe to Catalogue updates and contact government Data Custodians, who are responsible for the information and can help answer questions about the data.

Acceptance Criteria

• [ ] park name has open data licence in the bc data catalogue
  • [ ] the public can access this dataset
  • [ ] public knows what this data set is
  • [ ] public has a contact for this data set
  • [ ] can download a csv version of this data set

Given When Then

Given When Then

Development Checklist

• [ ] the dataset is published in BC Data Catalogue
• [ ] an Editor has been identified
• [x] an Editor account is created
  • [ ] Data Custodian authorizes to open an Editor account
  • [ ] a ticket is opened on service desk to create an Editor account
  • [ ] the approved ticket is reviewed by Data Custodian
• [ ] create...
• [ ] need to set up API end-point
• [ ] test environment...
• [ ] publish...
• [ ] data storage (only for publicly accessible data <150 MB)
• [ ] Contact information of "Contact Data Expert" button and in the "Contact" section of the list of contacts in the catalogue has been identified (most likely should be either a Data Custodian or a Data Steward)

Dependencies

• Blocked by: #123
• Blocking

Wireframe(s):

Workflows:

Definition of Ready

(Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

• [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
• [ ] UI meets accessibility requirements
• [ ] Unit tests are written
• [ ] Work is traceable in GitHub
• [ ] PR linked to ticket number
• [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

• [ ] Code is peer reviewed and has passed CI/CD tests

QA:

• [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
• [ ] Code is potentially shippable to the production environment
• [ ] Functional features have been tested and passed by QA
• [ ] UI components tested by designer
• [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
  • PO Review:
• [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
• [ ] Reviewed and approved by Product Owner

Notes

• The B.C. Data Catalogue is powered by CKAN open-source software and is managed by DataBC.

[JLWade]

moving to blocked because we need ODL and record published first