ME: edit record distributions
Description
This PR introduces the section on associated resources, allowing to add both download and service as distributions.
TODO: split and share components between annexes and associated resources.
Screenshots
Quality Assurance Checklist
- [X] Commit history is devoid of any merge commits and readable to facilitate reviews
- [ ] If new logic âī¸ is introduced: unit tests were added
- [X] If new user stories đ¤ are introduced: E2E tests were added
- [ ] If new UI components đšī¸ are introduced: corresponding stories in Storybook were created
- [ ] If breaking changes đĒ are introduced: add the
breaking changelabel - [ ] If bugs đ are fixed: add the
backport <release branch>label - [ ] The documentation website đ has received the love it deserves
Affected libs: feature-editor, ui-inputs, feature-dataviz, feature-record, feature-router, feature-search, feature-map, ui-elements, feature-notifications, feature-catalog, ui-catalog, ui-search, ui-layout,
Affected apps: metadata-editor, datafeeder, demo, metadata-converter, datahub, webcomponents, search, map-viewer,
- [ ] đ Build and deploy storybook and demo on GitHub Pages
- [ ] đĻ Build and push affected docker images
đˇ Screenshots are here!
Did a quick test and found this:
-
When trying to upload a file as a distribution, this error appears in the console and nothing happens:
; same for the "attached resources" field below actually
-
When clicking on the main block, the upload file dialog doesn't open
Otherwise looks good! thanks!
Just chiming in - "OGC API" title is misleading because there are so many OGC APIs (OGC API Maps, Features, Tiles...) Have a look at https://ogcapi.ogc.org/#standards
Just chiming in - "OGC API" title is misleading because there are so many OGC APIs (OGC API Maps, Features, Tiles...) Have a look at https://ogcapi.ogc.org/#standards
On the other hand it makes sense because an OGC API endpoint can provide many different information at the same place I think