All notable changes to this project will be documented in this file.
For each version, important additions, changes and removals are listed here.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Update documentation and README (#209)
- Move old metadata versions to folder (#209)
- Update JSON schema from (draft-07) to (Draft 2020-12) (#212)
- Update all tests (#212)
- Separate
timeseries - resolution
intoresolutionValue
andresolutionUnit
(#213) - Rename URI from
path
to@id
(#214) - Rename
source
-licenses
tosourceLicenses
(#215) - Update create template (#217)
- Update folder structure (#221)
- Update python version to 3.12 (#223)
- Update REUSE licenses for json (#225)
- Update example contributors and roles (#225)
- HotFix naming errors in some files related to the renaming of master to production #202
- Add OEMetadata version 2.0: #144
- Introduce a schema build system: #105
- The build files (schema & script) are maintained for each version (starting form v1.6.0) within the new directory called "metadata/(version)/build_source"
- The schema is rather long and complex. We split the long schema.json into modules. The modules are assembled in a json file that specifies the structure of the final schema.json, and it is called schema_structure.json.
- It uses JSON schema $ref elements to reference the schema modules, and it provides code to resolve the reference´s and generate the complete schema.json.
- Add code to generate an example.json based on the schema.json. We read the example values for each of the fields specified in the schema and generate the example. #105
- Add updated context.json (#154)
- Add
embargoPeriod
section with keysstart
,end
,isActive
(#155) - Add
path
tocontributors
(#157) - Add organization to contributors (#157)
- Add roles to contributors (#157)
- Add section for
Linked Data
keys (#159) - Add mandatory fields to the json schema (Iron Badge) (#160)
- Add key
copyrightStatement
tosources
(#162) - Add key nullable to fields section (columns) (#161)
- Add explicit json types (#166)
- Add key
topics
togeneral
(#170) - Add badge labels to documentation (#175)
- Implement schema build system v1: Enhance the resolve and generation module (#180)
- Add basic documentation with MkDocs (#184)
- Add key
publisher
tocontext
(#191) - Add array
authors
tosources
. (#193) - Add
year
tosources
(#194) - Add key
description
tocollection
and update badges (#195) - Add mappings to DCAT-AP to the documentation (#198)
- Add issue template for user kudos (#199)
- Remove comment field as it holds information on how to fill out the metadata and therefore should not be part of the actual oemetadata but the documentation. #105
- Update the schema json file content (schema generation still broken, add desired output) and fix the schema path in the script for generating examples (it pointed to an incorrect directory and file name) (#149)
- Update broken Link in key description example (#159)
- Update
resource/profile
toresource/type
(#164) - Update links in context.json and example.json for all versions (#167)
- Restrict the version number to only major and minor versions since 2.0 (#168)
- Update all descriptions and examples (#175)
- Build scripts use a settings file to share variables (#177)
- Refactor the
spatial
section and add new keys for location:address
,@id
,latitude
,longitude
and for extent:name
,@id
,resolutionValue
,resolutionUnit
,boundingBox
,crs
(#179) - Move
linkedData
keys to the top of the resource (#183) - Update order of keys in section context (#191)
- Remove email from contributors (#157)
- Remove all additionalProperties is false (#163)
- Remove duplicate keys from resources (#165)
- Remove linkedData section and keys (#176)
- Separate examples from description and put into its own key-value pair (PR#117)
- Add issue and PR templates (#116)
- Update context field (PR#114)
- Add GitHub actions to automate package build and upload process on test and production pypi index
- Fix missing json files in pypi oemetadata package
- Update context.json in latest & v151 to ensure ontologically annotated metadata can be sparkled #99
- Use GitHub projects to organise releases
- Add new example table to show connection to OEO
- Add test for latest directory to CI [PR#74]
- Add tests for v151 [PR#81]
- Add release version directory for oem-v151
- Update
subject
to work with OEO - Rename and update
isAbout
to work with OEO - Rename and update
valueReference
to work with OEO - Improve documentation
- Update schema.json
- Update CHANGELOG.md and give names to releases
- Update CONTRIBUTING.md
- Add keys for linked data compatibility:
@context
,@id
,subject
,is_about
,value_reference
- Add context.json file
- Add licence information to README.md
- Clarify instructions for dealing with non-applicable keys (null) and missing values ("todo")
- Make key 13.2
timeseries
a list - Relocate development information from README.md to CONTRIBUTING.md
- Update all .json files to v1.5.0
- Reintroduce automated tests (CI) by switching form travis-ci to GitHub actions [PR#63]
- Updated schema.json for v1.5.0 now includes the new key
title
which describes the title of the current field [PR#56] adapted from [PR#43]
- Delete future directory
- Add directory for v1.4.1
- Add tests for v1.4.1
- Add current section to Changelog, documenting all changes in current branch and stage for release
- Extend black options, COMMAND tox -v now shows exactly what code must be reformatted
- Rename repository from "metadata" to "oemetadata"
- Add
timeseries
totemporal
- Add
context
object for project information - Add
object
tocontributors
to decide between data and metadata - Add
profile
toresources
according to datapackage standard - Add
encoding
toresources
according to datapackage standard - Add
schema
toresources
according to datapackage standard - Add
type
tofields
for data types - Add
primaryKey
- Add
foreignKeys
- Add
dialect
- Add
review
- Add
metaMetadata
- Add
_comment
- Rename
url
topath
according to datapackage standard
- OEMetadata version v1.3.0 metadata schema, example, template
- OEMetadata version v1.4.0 metadata schema, example, template
- Python implementation and tests for schema, example, template of v1.3.0
- Python implementation and tests for schema, example, template of v1.4.0
- Implementation of metaschema (draft07) and test of metaschema