Open Data Release ChecklistWe have developed a draft checklist of the things you should consider before releasing open data. The checklist includes explanations of each item in the list. The aim of the checklist is to support the release of open data. Thank you very much to those who contributed to the draft.Help us improve the open data release checklist. We have published the draft checklist as a Google Doc so that you can add comments or suggest changes to the checklist - we acknowledge that with your practical experience you may discover better ways of doing or explaining things, and we would be grateful for any suggestions.
Alternatively you can email your feedback and suggestions to opendata@stats.govt.nz.Data.govt.nzDGNZ_78ced4f8-f7a3-11e9-a89a-ce4c60babdf6Data.govt.nz helps people discover, learn and use open data easily; empowering, enabling informed decision making, and problem-solving for citizens and business alike.New ZealandersAlthough the checklist has been written with a New Zealand audience in mind, we have tried to make it relevant and useful to the wider global open data community.[To be named]Global Open Data Community[To be named]_78ced764-f7a3-11e9-a89a-ce4c60babdf6To support the release of open data._78ced8fe-f7a3-11e9-a89a-ce4c60babdf6Open DataIdentificationIdentify your data_78ceda98-f7a3-11e9-a89a-ce4c60babdf61[To be named][To be named]InventoryKnow your data assets_78cedc0a-f7a3-11e9-a89a-ce4c60babdf61.1[To be named][To be named]Good quality open data will come from well managed data, data which is managed as a valuable asset. In order to manage data well, you must first know and understand what data you have. Therefore, creating and maintaining a data inventory (catalogue) is an important step. It might seem a simple step, but it can be a bigger job than expected.
Here are some thoughts to guide your data inventory development:
* Focus on one business unit at a time
keep it simple, don’t create too many columns (this can lead to an overwhelming level of information gathering about each dataset and slow progress) - more on this later…
* Aim to make it public so that people can discover and understand what data is held by your agency. This means describing the datasets in a way that can be understood by both the public and the business unit.
Regarding columns in the inventory - in New Zealand we are developing inventories that include the following:
* DCAT standard metadata columns - used by the CKAN catalogue at Data.govt.nz
* plus columns for: Open? (Y/N); Could be open(Y/N); What’s required to address before release? Estimated date of release
* plus a few columns of choice by each agency that met their needs to manage the data in their context.
View an example data inventory file [Link].
The data inventories are created as machine-readable CSV files. This enables an easy way to semi-automate the update of Data.govt.nz through simple script to select rows where Open?=Y and convert them into a “Data.JSON” file saved on the agency website, where Data.govt.nz can harvest your listing to keep it up to date. Therefore by updating the inventory you can also update your open data listings on Data.govt.nz.
Other benefits -
The process of carrying out a data inventory can also lead to a number of other benefits, such as:
* surfacing of duplicate datasets (or multiple different versions of the same thing)
* a business unit realising that another business unit has data they want but didn’t know existed
* discovery of ownership issues with data sourced elsewhere - that need to be sorted out
* more conversation about whether data could be made open
more awareness of data, let alone open data, across the organisation
* conversations about the benefits of more transparency
* evidence for more resources to manage the ever growing volume of data_78cedda4-f7a3-11e9-a89a-ce4c60babdf6_78cedf48-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]WebsiteExamine website for information with data behind it_78cee0ba-f7a3-11e9-a89a-ce4c60babdf61.2[To be named][To be named]This can be part of your data inventory process but worth doing as a separate exercise. Examine your website content for information that must have data behind it, such as tables and graphs. These may be on pages or as part of published reports for download.
This exercise helps you realise where data might be sitting in your organisation that people have forgotten about. If the information has been browsed or downloaded then you have evidence of interest in the data behind it._78cee312-f7a3-11e9-a89a-ce4c60babdf6_78cee48e-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]OIAs & RequestsReview OIAs and data requests_78cee614-f7a3-11e9-a89a-ce4c60babdf61.3[To be named][To be named]Official requests for information or data can be a clear indication of demand that could be proactively met through open data. This source of information could also help you quantify savings that could be made by releasing the data, by reducing the time spent on responding to requests.
Some agencies now have the practice where if an official request leads them to prepare and release data to someone, they then publish the data for all to access going forward._78cee7a4-f7a3-11e9-a89a-ce4c60babdf6_78cee934-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]OutreachEngage and ask data user communities_78ceeaec-f7a3-11e9-a89a-ce4c60babdf61.4Indigenous PeoplesIndigenous data sovereignty --
Indigenous peoples’ rights to data are set out in the UN Declaration on the Rights of Indigenous Peoples (UNDRIP). Article 18 stipulates that Indigenous peoples have the right to participate in decision-making in matters that would affect their rights, in accordance with their own procedures.
That participation should be from designing the collection through to the publication and use of data, with the opportunity to work towards beneficial outcomes for indigenous peoples. Partnerships between data publishers and indigenous peoples help address all information needs and manage expectations and responsibilities between partners.
When using data, especially when making decisions affecting indigenous peoples, we have an obligation to ensure they have had appropriate participation in the collection and care of the data.
There may also be obligations under local treaties or law to consider (for example, the Treaty of Waitangi in New Zealand).[To be named]_78ceec86-f7a3-11e9-a89a-ce4c60babdf6_78ceee2a-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]ReviewReview your data_78ceefe2-f7a3-11e9-a89a-ce4c60babdf62[To be named][To be named]PrioritisationPrioritise data for release_78cef17c-f7a3-11e9-a89a-ce4c60babdf62.1[To be named][To be named]Of course, all data that’s non-personal and unclassified should be proactively released, but it can’t all be magically released at once. It does take time and effort, and there are a number of ways to prioritise which data to work on releasing first, it just depends on where your organisation is at on its open data journey.
If you’re just starting out then finding a dataset in high demand and that is likely to get used straight away to make an impact will be a good candidate to focus on first. Once the data has been used, tell the story. When people see how open data can be used for the benefit of others the resistance to open data starts to wane.
Another approach can be to use the expectation to openly release data as a lever to get data into better shape - for your own organisation’s purposes. Therefore choose a valuable dataset that needs lots of work to improve its management and quality - and use the fact you will be releasing it publicly as a driver to get better governance and process wrapped around it._78cef302-f7a3-11e9-a89a-ce4c60babdf6_78cef5f0-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Ownership & RightsAssess ownership and rights over data_78cef79e-f7a3-11e9-a89a-ce4c60babdf62.2[To be named][To be named]It’s important to establish the copyright over the data. Is it yours to release? Or is it actually owned by someone else? Has your organisation acquired the data under licence from someone else?
A tool to help you through what you can and can’t do if the data is not fully under your copyright is the Review and Release flowchart in the New Zealand Government Open Access and Licensing Framework (NZGOAL).
In order to release data you need to be sure you own it, and even then there may be reasons why it can’t be released. Therefore you need to review:
* how the data has been acquired?
* were there any caveats on the data being provided (for example, confidentiality)?
* was the data purchased? If so, are there any restrictions to releasing as open?
* Was the data sourced from a third party organisation with restrictions on its use?
* Is the dataset a blend of your data and somebody else’s? Are there restrictions on the use of the data from the other party?
If the data, or part of it is actually owned by someone else it does not necessarily mean it can’t be released, you can try communicating your intentions and get their agreement to do so._78cef942-f7a3-11e9-a89a-ce4c60babdf6_78cefadc-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Data SovereigntyConsider data sovereignty of indigenous people_78cefc80-f7a3-11e9-a89a-ce4c60babdf62.3Indigenous People[To be named]Has the data been considered in the light of the 2007 United Nations Declaration on the Rights of Indigenous Peoples? Is there local treaties to consider? for example in New Zealand, Te Tiriti o Waitangi.
Your review should consider how indigenous communities are represented in the data; what input have they had into the design of the data collection? What is the likely impact on them in publishing the data? Should there be further consultation before release?
Ideally a relationship should be established at the beginning of the data lifecycle, the design of the data collection, so that Indigenous people can be empowered to benefit from the data for their desired outcomes. By the time it comes to potential publishing of the data a collaborative approach to release will have already been worked out._78cefe2e-f7a3-11e9-a89a-ce4c60babdf6_78ceffd2-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]PrivacyConsider whether a privacy impact assessment is needed_78cf0176-f7a3-11e9-a89a-ce4c60babdf62.4[To be named][To be named]Always consider whether you need to do a privacy impact assessment. You may not need to if the data is something like the location of road signs, but it's a good habit to always think about whether there might be privacy concerns.
In New Zealand we have a very useful Privacy Impact Assessment Toolkit provided by the Office of the Privacy Commissioner, and it is recommended to use this to determine the level of impact and the appropriate measures to safeguard privacy.
A privacy impact assessment may not be required but you should always think through whether or not one is necessary.
You can later come back to these people you meet to ask for feedback on your beta API or trial dataset you’re preparing for release._78cf031a-f7a3-11e9-a89a-ce4c60babdf6_78cf04c8-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Political SensitivityConsider whether to conduct a political sensitivity review_78cf0680-f7a3-11e9-a89a-ce4c60babdf62.5[To be named][To be named]Its difficult to give examples, but you just need to be aware of what’s going on in the world outside. Sometimes it just might not be the best time to release your data when there are tensions in the public domain on a related issue. You may look to delay release of the data, or manage the release through extra effort to proactively communicate about it.
A political sensitivity review may not be required but you should always think through whether or not one is necessary._78cf090a-f7a3-11e9-a89a-ce4c60babdf6_78cf0ad6-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]RiskConduct a general risk assessment_78cf0ca2-f7a3-11e9-a89a-ce4c60babdf62.6[To be named][To be named]A general risk assessment covers any issues that don’t come under privacy or political assessments, such as commercial sensitivity, potential security concerns or the risk of the data being used to cause harm. The issues identified may not mean the data shouldn’t be published, but there may be actions required to manage the impact.
A general risk assessment may not be required but you should always think through whether or not one is necessary._78cf0e6e-f7a3-11e9-a89a-ce4c60babdf6_78cf1058-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]StandardsReview standards applicable_78cf122e-f7a3-11e9-a89a-ce4c60babdf62.7[To be named][To be named]Wherever possible you should adhere to open standards when releasing data, this is to ensure maximum access to the data that does not rely on any specific proprietary software.
As you’ll see after you have worked through this section, the sooner you consider standards the better because the impact downstream in the data lifecycle can be significant and may mean your data is less valuable to users if it is not consistent with other data they wish to combine it with.
What needs to be standard?Data Formats_78cf142c-f7a3-11e9-a89a-ce4c60babdf6_78cf1634-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user]Data formats --
The data should be published in an open, machine-readable format, and if possible, multiple formats is preferable (again to increase accessibility and usefulness of the data). Examples of open data formats are...
Tabular data:
* CSV
* XML
* JSON
Geospatial data:
* GeoJSON
* KML
* GML
* Esri Shapefile
A CSV file may also serve as a geospatial file if it contains two columns for longitude and latitude values.
To learn more about open geospatial formats, go to GIS Geography.[To be determined]Metadata_78cf181e-f7a3-11e9-a89a-ce4c60babdf6_78cf1a08-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user]Metadata standards --
When releasing data, you should check to see if there is already a standard way to describe your data through metadata. The benefit of doing this is to ensure that your data is consistently discovered along with other like datasets through searches; to help data users to understand whether your data is likely to be compatible with other data they are looking to combine it with.[To be determined]Content_78cf1c06-f7a3-11e9-a89a-ce4c60babdf6_78cf1dfa-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user]Content standards --
There are two levels of content standards, record level and variable (attribute) level.
At record level we are concerned about what pieces of information we collect to describe the event/instance that the data is about. For example, datasets on tsunami evacuation zones may want to contain a minimum of evacuation zone type; location; height; shape area; and shape length.
So check to see how others are releasing the data, and where appropriate, talk to other agencies in the same industry.
Variable level content standards are concerned with having consistent and comparable values in variables within a record such as name, address, date of birth, gender etc..
For example in statistical data about people, when comparing based on gender, it's important that all data has been collected with the same list of options and have values are consistent like having “Male” instead of just “M”.[To be determined]Data Collections_78cf1fda-f7a3-11e9-a89a-ce4c60babdf6_78cf21c4-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user]Data Collection Standards
For data to be comparable it’s important it to be collected consistently, not just in terms of content standards, but also the method of data collection.
For example, water quality. What are the types of particles that are typically collected by sensors, and what is the typical level of accuracy of the sensors? What other factors are considered and recorded to determine water quality such as ecological health?
Good context with data helps others to understand how data has been collected and can enable a sector to move towards their own standard if no useful international standard already exists. An example of helpful context on how data is collected is this description by the Waikato Regional Council on how they measure water quality at https://www.waikatoregion.govt.nz/environment/natural-resources/water/rivers/healthyrivers/how-we-measure-quality/[To be determined]APIs_78cf23a4-f7a3-11e9-a89a-ce4c60babdf6_78cf258e-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user]API standards --
It's important that your data API adheres to open standards. If not, your data may be inaccessible to people that do not have/cannot afford the proprietary software required to connect to your API. A data user should be able to query your API using commonly known commands and query language.
For more information about API standards, go to:
Digital.govt.nz https://www.digital.govt.nz/standards-and-guidance/technology-and-architecture/application-programming-interfaces-apis/[To be determined]AuthorisationGain appropriate approval to release_78cf2778-f7a3-11e9-a89a-ce4c60babdf63[To be named][To be named]Every agency may have a different authorisation process, and different points along the journey to gain approval to release data. In some cases you may need to get approval very early in the piece when working through this checklist. In other cases, a governance committee may expect to know the outcomes of privacy, political and general risk assessments and what is proposed to manage any risks. Therefore the assessments should be done before seeking authorisation.
One possibility is to work towards developing a procedure that is approved, and where if certain criteria are met in assessments the release is “pre-approved”, with only exceptions needing to be formally approved._78cf294e-f7a3-11e9-a89a-ce4c60babdf6[To be named][To be named]_78cf2b24-f7a3-11e9-a89a-ce4c60babdf6_78cf2d40-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]PreparationPrepare your data for release_78cf3006-f7a3-11e9-a89a-ce4c60babdf64[To be named][To be named]CleaningClean the data_78cf3484-f7a3-11e9-a89a-ce4c60babdf64.1[To be named][To be named]Data cleaning is the process of correcting obvious errors or making things more consistent (eg. putting ‘city’ in the City variable/column rather than in Address Line 2).
The amount of cleaning depends on the size of the data and how it has been collected. Ideally cleaning would be done in its primary location (eg. in the database behind a business/service delivery system), rather than after you have extracted data out separately for release, otherwise you will only have to repeat the process when the data ise re-extracted to release an update._78cf368c-f7a3-11e9-a89a-ce4c60babdf6_78cf3baa-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Confidentialisation_78cf4186-f7a3-11e9-a89a-ce4c60babdf64.2[To be named][To be named]_78cf4442-f7a3-11e9-a89a-ce4c60babdf6_78cf4672-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Metadata_78cf48a2-f7a3-11e9-a89a-ce4c60babdf64.3[To be named][To be named]_78cf4adc-f7a3-11e9-a89a-ce4c60babdf6_78cf4d2a-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Dictionary & ERDData dictionary and Entity Relationship Diagram_78cf4f5a-f7a3-11e9-a89a-ce4c60babdf64.4[To be named][To be named]_78cf519e-f7a3-11e9-a89a-ce4c60babdf6_78cf53f6-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]DocumentationProvide documentation_78cf56da-f7a3-11e9-a89a-ce4c60babdf64.5[To be named][To be named]Documentation including:_78cf5928-f7a3-11e9-a89a-ce4c60babdf6_78cf5b76-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]ContextProvide context about collection and purpose of the dataset_78cf5dba-f7a3-11e9-a89a-ce4c60babdf64.5.1[To be named][To be named]To help data users understand the data and to use it appropriately, it’s important to provide good context information, such as:
* the purpose the data was originally collected for
* how it was collected
* important concepts that might need explaining for clarity
* any limitations (such as the accuracy level of sensors or known bias in samples)
And anything else that you can think of that will help data users make the best use of the data (and manage any inappropriate use through misunderstanding).
Sometimes all you need a paragraph, this example at the source of biosecurity plant pest data at Marlborough District Council conveys a lot of useful information very succinctly:
“This Council dataset records where plant pests have been found in the past by Council staff or through confirmed reports. Strong caution is advised as there may be other infestations in Marlborough that have not yet been captured in this dataset. If you suspect any other infestations that are not marked on this map, please contact the Biosecurity team at Council. This dataset does not distinguish the density or nature of the infestation at a given site. A marked area could range from heavily infested to only scattered plants. Either way, there is still a spread risk from both. Data updated weekly.”
In just one paragraph they have communicated how the data is collected; cautioned about a weakness that there might be gaps; how you can help them fill those gaps (both managing the risk and inviting engagement and contribution from data users); explained how to interpret what you will see in the data; and how frequently the data is updated.
More examples:
Helpful context on how data is collected is this description by the Waikato Regional Council on how they measure water quality: https://www.waikatoregion.govt.nz/environment/natural-resources/water/rivers/healthyrivers/how-we-measure-quality/
Building outline data from Land Information New Zealand (LINZ): https://nz-buildings.readthedocs.io/en/latest/introduction.html?fbclid=IwAR1eX2_ozq5TamgkQsyaUMpit1uys3DeADdf_zikqrOG86CDkH7iGc9Gm58_78cf5ffe-f7a3-11e9-a89a-ce4c60babdf6_78cf6256-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]ExplanationExplain the data_78cf64ae-f7a3-11e9-a89a-ce4c60babdf64.5.2[To be named][To be named]In addition to context, it may be helpful to describe what some variables mean, especially in scientific data. It may be possible to have one reference piece that supports the understanding of a number of related datasets._78cf6706-f7a3-11e9-a89a-ce4c60babdf6_78cf694a-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]APIsExplain how to use the API (if API available)_78cf6b98-f7a3-11e9-a89a-ce4c60babdf64.5.3[To be named][To be named]APIs can be subtly different to interact with, having slightly different commands and syntax. Having sum guidance for developers on how to use the API can speed up their access to the data considerably, saving their time and achieving impact more quickly.
An example of the kind of help needed to help developers going is at the New Zealand Charities Register open data:
https://www.charities.govt.nz/charities-in-new-zealand/the-charities-register/open-data/_78cf6ddc-f7a3-11e9-a89a-ce4c60babdf6_78cf7034-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]QueriesProvide query examples (if released through an API)_78cf7296-f7a3-11e9-a89a-ce4c60babdf64.5.4[To be named][To be named]Building on the idea of providing guidance to use your API, it is very helpful to data users, especially those unfamiliar with your specific API platform, to provide some examples of how to query your API. This will assist them in accessing the data and getting on with using it much more quickly, and for some, examples may be all they need.
The New Zealand Charities Register API user documentation does this well:
https://www.charities.govt.nz/charities-in-new-zealand/the-charities-register/open-data/_78cf74f8-f7a3-11e9-a89a-ce4c60babdf6_78cf7764-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]ReleaseDetermine release frequency and process_78cf7ab6-f7a3-11e9-a89a-ce4c60babdf64.6[To be named][To be named]When considering the frequency of updating the data you need to consider what work and/or process is required to update the released data. You also need to consider what is useful to the consumers of the data. This may require some engagement with data users early on so you can prepare to meet expectations that lead to good use of the data.
Some different examples to consider:
* Statistical data - consider the level of work required to prepare for release, and determine whether there are existing release schedules and data preparation processes that the dataset would fit in with
* Data from sensors - is the data most valuable in real-time? If so, can it be released in real-time? Or does the situation call for some data cleaning or processing before release?
* Counts (eg. traffic counts) - what frequency is most useful for data consumers? hourly, daily, weekly or monthly?
* Registers - how often do changes occur? How often is the register accessed? Are daily updates required by users or would weekly or monthly be sufficient?_78cf7e44-f7a3-11e9-a89a-ce4c60babdf6_78cf80b0-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]MaintenancePlan for maintenance_78cf8344-f7a3-11e9-a89a-ce4c60babdf64.7[To be named][To be named]As you prepare to release the data, ensure that the appropriate process and procedures are in place to ensure the regular update of the data. In some cases this may be closely tied with a business process or it may mean setting up an automated update process. In other cases, you may need to ensure a way of alerting someone that an update is expected.
For some data you may need to consider how you want to present time-series. If publishing static files, do you want to publish snapshots in time in separate files or combine additional time periods into one file?_78cf85e2-f7a3-11e9-a89a-ce4c60babdf6_78cf8876-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Engagement & TestingEngage users and test pre-release_78cf8b14-f7a3-11e9-a89a-ce4c60babdf64.8[To be named][To be named]One way to get impact from releasing open data is gather a community around the data along the journey towards releasing it. In addition to helping you design a good data release, this community can also help you test your data and the access to it (eg. API) and give you feedback from a user perspective before you go live._78cf8db2-f7a3-11e9-a89a-ce4c60babdf6_78cf9050-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Implementation[To be described]_78cf92ee-f7a3-11e9-a89a-ce4c60babdf65[To be named][To be named]Formats[Use] Open Data formats_78cf9582-f7a3-11e9-a89a-ce4c60babdf65.1[To be named][To be named]An open data format is a format that is format for storing digital data, defined by a published specification usually maintained by a standards organization, and which can be used and implemented by anyone. An open format does not require specific proprietary software to access the data, and is machine-readable.
To read more about open data formats and a table of examples, go to: https://www.data.govt.nz/manage-data/policies/nzgoal/guidance-note-2/._78cf9820-f7a3-11e9-a89a-ce4c60babdf6_78cf9ab4-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]APIsUse Open API standards_78cf9d34-f7a3-11e9-a89a-ce4c60babdf65.2[To be named][To be named]An open API is one that conforms to requirements defined by a published specification usually maintained by a standards organization. An open API does not require any proprietary system to access it, and uses well known commands and standard protocols for interaction.
To read more on open API standards and guidelines go to: https://www.digital.govt.nz/standards-and-guidance/technology-and-architecture/application-programming-interfaces-apis/
For information on the qualities of a good open data API from the user’s perspective, go to:
https://www.data.govt.nz/manage-data/releasing-data-on-data-govt-nz/qualities-of-a-good-open-data-api/_78cf9fdc-f7a3-11e9-a89a-ce4c60babdf6_78cfa25c-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]LicensingLicense for reuse_78cfa5d6-f7a3-11e9-a89a-ce4c60babdf65.3[To be named][To be named]With the notable exception of the US Federal government, publications by governments around the world are subject to copyright by default. This means when publishing data on the web, by default the ability for people to reuse it is heavily restricted.
So to make data open, it is critical to license it for reuse, to explicitly give permission that overrides copyright restrictions. Some countries have written their own open licences (such as the UK Open Licence), but many countries have a policy of using the Creative Commons Licences, and provide guidance on how to apply them.
For an example of policy and guidance on how to apply Creative Commons Licences to government data, information and publications, refer to the New Zealand Government Open Access and Licensing framework (NZGOAL)._78cfa860-f7a3-11e9-a89a-ce4c60babdf6_78cfab08-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Disclaimers & WarningsConsider need for additional and prominent disclaimers/warnings
_78cfad9c-f7a3-11e9-a89a-ce4c60babdf65.4[To be named][To be named]At the point of release to reduce reliance risk to people if their safety is at stake, you may need to consider the need for additional disclaimers or warnings (e.g., ‘this data should not be used for X, Y, Z purposes without independent validation; depends entirely on the context as to whether any such statement is desirable)._78cfb030-f7a3-11e9-a89a-ce4c60babdf6_78cfb2ba-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]PublicationPublish data_78cfb562-f7a3-11e9-a89a-ce4c60babdf65.5[To be named][To be named]OK, so now you’ve done it… Congratulations! :)
But the job isn’t over yet, keep going on the list…_78cfb800-f7a3-11e9-a89a-ce4c60babdf6_78cfba9e-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]DocumentationPublish documentation published_78cfbd3c-f7a3-11e9-a89a-ce4c60babdf65.6[To be named][To be named]Ensure your documentation is easily discoverable near the source of the data._78cfc016-f7a3-11e9-a89a-ce4c60babdf6_78cfc3c2-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]FeedbackEnable data users to provide feedback_78cfc71e-f7a3-11e9-a89a-ce4c60babdf65.7[To be named][To be named]Also discoverable near the source of the data there should be an option for data users to provide feedback, either on the data itself or the ease/difficulty of access.
Ensure there is a process behind the feedback option so that you can be responsive and take action as required. Responsiveness to feedback can build trust and relationships that can be mutually beneficial, especially for future releases of data._78cfc9c6-f7a3-11e9-a89a-ce4c60babdf6_78cfcdfe-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Reuse StoriesInvite users of the data to tell you how they are using the data._78cfd13c-f7a3-11e9-a89a-ce4c60babdf65.8[To be named][To be named]Don’t be shy, ask users of the data to tell you how they are using the data. Explain that the more stories of use and impact from the data will help the business case for investing in more data releases.
You could even commit to publishing their story as a case study. This is often a win-win because it not only helps your case for investing in more open data, but is often good publicity for the data user and their business or advocacy/cause._78cfd420-f7a3-11e9-a89a-ce4c60babdf6_78cfd7a4-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]Catalogue / PortalList published data on a central government data catalogue or portal_78cfdb1e-f7a3-11e9-a89a-ce4c60babdf65.9[To be named][To be named]Once you have published data, listing it on a central government data catalogue or portal can make it much more easily discovered and used.
For a single dataset this is often only a 10 minute job, providing a standard set of metadata about the dataset. If you are regularly releasing open data there may be ways to to bulk update or harvest your data listing.
Your central portal should have information about your options and how you go about updating the catalogue, for example at Data.govt.nz._78cfdde4-f7a3-11e9-a89a-ce4c60babdf6_78cfe186-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]PromotionTell the world about the availability of your data_78cfe492-f7a3-11e9-a89a-ce4c60babdf65.10[To be named][To be named]Don’t just list the data and sneak away, tell the world about it. The more people know its there, the more likely people who have a need for it will become aware and use it. So tell any community you have built around your data, share on social media, newsletters, Meetups and conferences if appropriate.
And as people use it, gather the stories on how they have used it and share on all your channels._78cfe726-f7a3-11e9-a89a-ce4c60babdf6_78cfeac8-f7a3-11e9-a89a-ce4c60babdf6[To_be_inserted_by_user][To be described][To be determined]_78cfedfc-f7a3-11e9-a89a-ce4c60babdf62019-10-25_78cff0b8-f7a3-11e9-a89a-ce4c60babdf6OwenAmburOwen.Ambur@verizon.net