-
Notifications
You must be signed in to change notification settings - Fork 59
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
Where are new metadata entry XMLs stored? #9
Comments
The xml files are stored within ElasticSearch. Within the index there is an es type "item", and another type "clob". The xmls are within the "clob" type. |
Thanks @umacgillivray . Would you know of an effective way of exporting these from ElasticSearch? |
to where? |
Java from within geoportal would look something like this ` import com.esri.geoportal.lib.elastic.util.Scroller; public static void testExport() throws Exception { |
Basically I'm just looking to export these to the local geoportal server as individual XMLs. |
I appreciate the help @umacgillivray . Would you be able to guide me as to where I would enter this code? Which file(s) would need to be edited? I am not very proficient in Java unfortunately. Thanks. |
Can XMLs be exported server side via editing the JavaScript? I'm getting a grasp of the save function. MetadataEditor.js
|
Would this be better done as an enhancement to the geoportal-harvester? Connect to a geoportal 2.0, export to folder. |
yes! especially since harvesting to a folder is already supported. you would create an input broker for Geoportal Server Catalog 2.x. adding @pandzel in case he has already worked on such a broker for harvester |
As the new Geoportal does not use a database, I was wondering where the user created metadata (through metadata editor) files stored?
When a user creates metadata is it stored as an XML file on the server? If not, can this be configured to do so?
Thank you.
The text was updated successfully, but these errors were encountered: