-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unpack schema sample data into folders, produce mef files at build time #7457
Conversation
08ccdee
to
90f27d3
Compare
@ianwallen you expressed interest in this activity |
Testing these sample records, appear to work as before - however the records content themselves are outdated. |
@ianwallen do not have sufficient permissions to request your review. If anyone else is interested this is a straightforward change to test locally. |
@fxprunayre can this be merged now? I wish to have an updated sample records to document online-help functionality. |
No objection here, but I'm a bit short in time to check it. If you've tested it on projects with @josegar74 or @ianwallen don't hesitate to go ahead. |
@jodygarnett about your comments in the PR:
MEF is just a regular zip with a folder structure.
It seems a MEF 2 format, that allows multiple metadata included. MEF 1 format only allows 1 metadata. |
schemas/iso19139/src/main/plugin/iso19139/sample-data/photographic_session/metadata.xml
Outdated
Show resolved
Hide resolved
This should be good to merge and backport |
feedback has been addressed; I have also rebased against main to ensure the changes are clean. |
cdea5e1
to
8ce7e25
Compare
I did a sample build on my system and I looked for
Can you double check iso19115-3.2018 to ensure that it is properly creating the sample-data folder |
I concur, it did not show up as expected - let me fix that. Checking dublin core the empty folders are not included:
Comparing with main branch which includes empty folders:
Update: I was able to fix this with a change to the ant zip task : whenempty="create" |
iso19115-3.2018 service_record.mef now reports back:
And this is included in the plugin:
|
With feedback addressed I am going to rebase, and am in position to merge on Monday. @fxprunayre you are still listed as a requested reviewer, let me know if you still wish to review this change. Update: Rebased done for a clean change history suitable for backport |
3ee1f38
to
0de59c9
Compare
Signed-off-by: Jody Garnett <[email protected]>
Signed-off-by: Jody Garnett <[email protected]>
Signed-off-by: Jody Garnett <[email protected]>
0de59c9
to
43a5369
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine, @jodygarnett as the 4.4.2
release is next week, I moved the target to 4.4.3
.
Why not merge now? |
…ld time (#7457) * unpack iso19139 sample data, create mef file at build time Signed-off-by: Jody Garnett <[email protected]> * unpack iso19155-3.2018 sample data, create mef file at build time Signed-off-by: Jody Garnett <[email protected]> * unpack dublin-core sample data, create mef file at build time Signed-off-by: Jody Garnett <[email protected]> --------- Signed-off-by: Jody Garnett <[email protected]>
Following example of HNAP plugin metadata101/iso19139.ca.HNAP#350 I had offered to do the same change for core-geonetwork.
mef
files.The iso19115-3.2018 sample data for service record was ... odd:
zip
file, not amef
file.This build change is prepared to update sample data for #7363
Checklist
main
branch, backports managed with labelREADME.md
filespom.xml
dependency management. Update build documentation with intended library use and library tutorials or documentation