Skip to content
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

Publish metadata with a status of “Draft” if metadata is invalid #181

Closed
eggwhites opened this issue Jul 27, 2015 · 5 comments
Closed
Assignees
Milestone

Comments

@eggwhites
Copy link
Contributor

Please add the ability to publish metadata with a status of “Draft” if metadata is invalid, instead of rejecting the document. This allows users to publish metadata and then open it up in the geoportal metadata editor for further editing (understanding also the limitations of the editor, as cited in https://github.com/Esri/geoportal-server/wiki/Online-form-editing-for-all-publication-methods).

@gcampanile
Copy link
Contributor

Fully agree. I would suggest some more enhancements to simplify the process of converting/ adapting an existing repository:

  • publish (from a file) a record in draft if invalid (as requested by eggwhites)
  • publish (when harvesting) records in draft if invalid. This can also be controlled by adding a flag to the repository to choose the behaviour, discard or publish in draft.
  • Use a specific profile editor for a metadata record This is very useful with custom profiles, to avoid manually editing of XML files.

Gianni

@zguo
Copy link
Collaborator

zguo commented Apr 20, 2016

while we can try to publish and set the document status to draft mode, what the publisher will do with it afterwards as some of the invalid record might not be able to open by an editor? in case of harvesting you may have vast amount of records published as draft. it seems not realistic to manually edit large amount of invalid data either.

@smrgeoinfo
Copy link

I agree, if a harvest yields a lot of invalid records, manually editing individual records is not a great solution, but for the case where there is a manageable number of problem records, its still a desirable feature. As far as content that might be lost by the editor, I'd say its up to the catalog manager to handle that in an input XSLT that either puts content where it will be preserved (like putting CSDGM entity attribute metadata in the abstract), or puts a note in the metadataMaintenance section to note that some content was lost in translation...

@zguo
Copy link
Collaborator

zguo commented Apr 21, 2016

We can add a parameter to gpt.xml, set the option to false by default, an admin can enable draft mode if they choose to and know the implication.

@zguo zguo added this to the 1.2.7 milestone Apr 21, 2016
@pandzel-zz
Copy link

Registration page, Upload page - checkbox when checked then metadata will be upload as draft if validation failed. Code in 'develop' branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants