Standard / Feature catalogue / Replace ISO19110 by ISO19115-3 #6545
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using ISO19115-3, editor can create records which: * can only describe a feature catalogue description. * or can describe a dataset with a feature catalogue embedded (or linked with a citation). Those records are indexed with a field `resourceType=featureCatalog` which enable search when linking feature catalogue in the editor to other records (both type of records can be linked ie. record with only a feature catalogue description or a record with an embedded one). While indexing feature catalogue: * name is title, * fieldOfApplication is abstract when the record is only a feature catalogue. TODO: - [ ] Check which scopeCode is more appropriate eg. featureType ?) - [ ] Editor / Full view / If only a feature catalogue, it could be better to open the content tab directly (as there is no identification) - [ ] Add conversion from ISO19110 to ISO19115-3 - [ ] Remove old ISO19110 schema
…ogue only record).
|
Kudos, SonarCloud Quality Gate passed!
|
…tion only if contents in, title and abstract for feature catalogue.
…feature catalog, the content tab.
…add missing translations.
…feature catalog, the content tab. Take version from @CMath04 - https://github.com/GIM-be/dcat2/blob/master/core-geonetwork-patches/0009-122116-Active-first-visible-tab-in-view-instead-of-a.patch
Customize fuzziness or wildcard in queryBase in CatController if required. Adding wildcard at start and end will return no results when search contains more than one word.
Sample configuration to only display citation for series/dataset/nongeographicdataset.
Index field may be an array. Add support for this by intersecting condition values and field values.
…ing codelist value.
josegar74
reviewed
Nov 15, 2022
| if (values.includes(recordValue)) { | ||
| cb(); | ||
| if (angular.isArray(recordValue)) { | ||
| if (values.filter((value) => recordValue.includes(value)).length > 0) { |
There was a problem hiding this comment.
Produces the following error in the log file:
SEVERE: /catalog/components/utility/UtilityService.js:384: ERROR - this language feature is only supported in es6 mode: short function syntax. Use --language_in=ECMASCRIPT6 or ECMASCRIPT6_STRICT to enable ES6 features.
if (values.filter((value) => recordValue.includes(value)).length > 0) {
To check to use Lodash.
There was a problem hiding this comment.
Fixed. Can be done with JS.
|
@fxprunayre the table mode for codelist elements doesn't allow to add new entries, is that something that can be added easily in the configuration? |
<for name="gfc:listedValue"/>
</flatModeExceptions>does it.
|
josegar74
approved these changes
Nov 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using ISO19115-3, editor can create records which:
Those records are indexed with a field
resourceType=featureCatalogwhich enable search when linking feature catalogue in the editor to other records (both type of records can be linked ie. record with only a feature catalogue description or a record with an embedded one).Depending on how much reused are feature catalogue, users can decide to use the embedded mode or not.
Using ISO19115-3 for feature catalogue also add support for multilingual feature catalogue.
While indexing feature catalogue:
cat:nameis the resource title,cat:scopeis the resource abstract when the record is only a feature catalogue.Linking the feature catalogue to a dataset
From the editor panel
In the record view
Embedded feature catalogue
A feature catalogue only
Record view for feature catalogue
Editing feature catalogue in ISO19115-3
Editing was working fine.
gco:UnlimitedIntegertype.gfc:aliasesISO19110 migration to ISO19115-3
The process name is
iso19115-3.2018-schemaupgrade. When running the process, the schema is automatically updated to ISO19115-3 (as the process ends with-schemaupgrade)ISO19110 schema is deprecated
Migration can be previewed using http://localhost:8080/geonetwork/srv/api/records/7135698b-3c1c-4f88-9d4e-e19ae7bbf07e/formatters/iso19115-3_2018?output=xml
ISO19139
Future work
mcc:MD_ScopeCodeis more appropriate eg. featureType ?)identificationInfois mandatory from ISO19115-3 point of view (https://github.com/geonetwork/core-geonetwork/blob/main/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/schema/standards.iso.org/19115/-3/mdb/2.0/metadataBase.xsd#L63-L64). Creating a record with only acontentInfoelement is invalid for XSD validation.