osgeo / mdme

Model Driven Metadata Editor (MDME): web application for geospatial metadata editing

The Open Source Geospatial Foundation

The Open Source Geospatial Foundation is a not-for-profit organization to empower everyone with open source geospatial. The software foundation directly supports projects serving as an outreach and advocacy organization providing financial, organizational and legal support for the open-source geospatial community. OSGeo works with our sponsors and partners to foster an open approach to software, standards, data, and education.

OSGeo has US 501(c)(4) legal status as a not-for-profit organization

This repository contains official branding, documents, and correspondence. Access is limited to volunteers working with our foundation committees.

License

All work here is copyright The Open Source Geospatial Foundation. Unless otherwise stated this content is made available to you under an appropriate Creative Commons license.

Document licenses for software developers:

• CCBY - permissive license similar to MIT or BSD allowing content to be remixed by other authors, as long as they give us a credit somewhere. This is a great choice for outreach and increases our brand awareness.

• CCBYSA - protective license similar to GPL allows content to be remixed by other authors, as long as what they are writing is also using a share-alike license.

• CC0 - Creative Commons public domain tools are used for outreach where we want the information to have as far a reach as possible. When using this approach we do not even ask for attribution! We have to be careful using this license to avoid including any content or photos that we did not create ourselves.

Not all of our content is licensed for modification:

• CCBYND - some documents are not useful to share in a modified form: our organization charter, memorandums of understanding with partners, official legal documents, letters of recommendation, letters of support. In these cases we allow free distribution, but not modification, of said content. Authors may still quote or cite these materials, and this GitHub repository provides a stable URL. Be sure to include the revision when citing as these documents change over time.

Copyright

The Open Source Geospatial Foundation maintains copyright on all materials in the repository (except otherwise noted). This material was produced by our volunteers on behalf of our organization or donated via a pull request to our foundation in accordance with our contributor license agreement.

What does "except otherwise noted" mean? Some CCBYSA photos are used in our presentation templates and branding guide. We have included these photos in our repository, appropriately crediting the original authors in the initial commit message and in the directory README.md file.

mdme's Issues

check if codelists from ./public/codelists can be used

extent inrae metadata profile with inspire fields

send mail to clement with inspire fields

• scale/resolution
• projection info
• priority dataset
• inspire theme
• geographic scope
• conforms to inspire regulation

select from a library of contact points

instead of adding similar contact details over and over (you could add them to the template though), would be nice to select a contact from a list and have all contact details auto populated

• requires a mechanism to capture contact details in local browser storage
• a widget which allows to select from the list (auto-complete)

import from ogc-api:features

similar as import from wms, fetch the collection metadata from an ogc-api:features endpoint

select keyword from thesaurus

in stead of typing out a thesaurus and a keyword, introduce a mechanism which presents a selection option for keywords of a thesaurus.

Initially we could store the thesaurus as json in codelists, but alternative is to load the thesaurus from a skos repository using sparql or directly as json-ld/ttl

for example: https://github.com/rapw3k/glosis/blob/master/glosis_cl.ttl

extend import iso19139

currently picks up only 2 properties, should we implement more or delegate to a webservice which uses owslib or pygeometa to import the record?

improve import wms

• if a metadataurl is provided, try to import the record and use it
• else set a default metadata:id
• if a authority&identifier is provided, use as dataset-identification

extents/spatial is an array, not dict

CURRENTLY is set as dict, same for temporal extent

Keywords to move from key-Val to array

See #22

build latest version and deploy at github.pages on commits

for example as documented at
https://blog.logrocket.com/automatically-build-deploy-vuejs-app-github-pages/

option to run the app as a local native app

double click a xxx.mcf.yml file to open the editor to modify the file and save it

yusing a platform such as electron, see for example https://itnext.io/electron-application-with-vue-js-and-vuetify-f2a1f9c749b8

enable multiple profiles at once

Currently you have to set a profile (opgapi-records, mcf, datapackage) in settings. Instead would be nice to load the relevant schema file when a new file is created or imported.

• New record -> Select profile -> Load schema -> Open editor
• Open record -> Detect schema of the record -> load schema -> Open editor
• Export record -> dedicated exports for schema's (datapackage and ogc-api:records are based on json, mcf is yml).

enable image upload

esri introduced a mechanism in which an uploaded image (thumbnail) is embedded in the metadata record as a base64 encoded string. this could be an interesting approach to let users upload a thumbnail image via the interface and store it within the metadata document.

alternative is that uploaded images are persisted separately from the record and a reference to the uploaded image is stored on the record, this is how github for example manages included images.

pull and push to ogcapi-records

Pull a record from ogcapi records, for example https://demo.pygeoapi.io/master/collections/dutch-metadata
and load it on the form for editing, entry could be a search against the ogcapi-records, or just the url of the item.

If the ogcapi-endpoint supports transactions, option to push the record. User would need to authenticate against the service (SAML/OAuth token or basic authentication)

why is metadata section red, with all fields populated?

reproduce:

• open mcf editor
• populate all metadata fields
• navigate to next section

expected: metadata is ok

observed: metadata section is still red (is there an error message in logs?)

create a widget to set a bounds object on the json

introduce a leaflet map, which people can use to navigate to the relevant area, then draw a box (or point/line) or something?

See also koumoul-dev/vuetify-jsonschema-form#378

support pygeometa service in pygeoapi for record validation/generation

See commit geopython/pygeometa#183 (released in pygeometa 0.13)

This introduces validation and generation (conversion) processes on pygeoapi.

mdme can use these services to validate records (on completeness) and convert to iso19139, dcat etc...

check multilingual

can we be flexible to support both:

title: "foo"

as well as

title:
   en: foo
   fr: faa

use demo.pygeoapi.io to convert mcf to iso/dcat/...

introduce an export panel with option to select the desired metadata schema (as provided by the metadata service in demo.pygeoapi.io)

layout of plus-item button to tight

needs more spacing, is this a problem on vjsf?

could add extra display class to item, but would like it to be default behaviour