Admin / Harvesting / Order options according to processing. #6221
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
Rework harvesting configuration pages in order to have a clear idea of the various harvester steps in order. Instead of basic/advanced configuration section, define first: * Connection to the data source * Configuration of the response processing. In the processing order elements as they are done server side. For harvester like CSW where many optional steps can be applied, user knows now when xpath filtering is done, if XSL transformation is applied before batch edits, ... Add some icons for main sections.
|
@fxprunayre Looks good! Found 2 things that probably have been there already:
|
No, check titellus#92, you copy an existing harvester and you can paste the config as a new one (it makes easy to share harvester config between catalogues). |
But better "Paste harvester config" |
fxprunayre
added a commit
that referenced
this pull request
Apr 5, 2022
|
Ok, now I understand, yes, 'paste' would better fit the option |
Done in the transifex update PR #6225 (to avoid conflicts) |
MichelGabriel
approved these changes
Apr 5, 2022
fxprunayre
added a commit
that referenced
this pull request
Apr 6, 2022
* i18n / Transifex updates. * Admin / Config / UI / Restore HTML link in translations. * i18n / Add missing key. * i18n / Fix paste harvester config #6221 (comment).
fxprunayre
added a commit
that referenced
this pull request
Nov 21, 2022
* Add XML file support * Add support for multiple URL * Clarify options order (follow up of #6221) * Add all missing translations * Use XSL conversion combo instead of free text
7 tasks
fxprunayre
added a commit
that referenced
this pull request
Jan 18, 2023
* Harvester / Simple URL / Improvements * Add XML file support * Add support for multiple URL * Clarify options order (follow up of #6221) * Add all missing translations * Use XSL conversion combo instead of free text * XSL / Conversion / Remove transformation relying on a plugin not available by default * XSL / Conversion / Remove transformation relying on a plugin not available by default * Harvester / SimpleURL / Add support for ODS v2 API * Harvester / SimpleURL / Report error when path are wrong. Use Pointer for UUID retrieval (required for ODS API v2)
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.
Rework harvesting configuration pages in order to have a clear idea of
the various harvester steps in order.
Instead of basic/advanced configuration section, define first:
In the processing order elements as they are done server side. For
harvester like CSW where many optional steps can be applied, user
knows now when xpath filtering is done, if XSL transformation is applied
before batch edits, ...
Add some icons for main sections.
eg. for CSW - define URL, then all search options, then configure response processing and privileges