Changes between Version 1 and Version 2 of HidingMetadata


Ignore:
Timestamp:
Oct 3, 2012, 8:23:26 AM (12 years ago)
Author:
jeichar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HidingMetadata

    v1 v2  
    44|| '''Contact(s)''' || [http://wiki.osgeo.org/wiki/User:Jeichar Jesse Eichar] ||
    55|| '''Last edited''' || ||
    6 || '''Status''' || Proposed for vote ||
     6|| '''Status''' || In Progress ||
    77|| '''Assigned to release''' || 2.9.x ||
    8 || '''Resources''' || Funding Swisstopo ||
     8|| '''Resources''' || Funding IFremer ||
    99|| '''Code''' || https://github.com/jesseeichar/core-geonetwork/commits/feature/jmeter ||
    1010
    1111== Overview ==
    1212
     13In certain circumstances it can be desirable to hide certain elements of metadata, for example if passwords or connection information is contained in the metadata.  This proposal allows these elements to be hidden when viewed by non-owner/administrator users.
    1314
    1415=== Proposal Type ===
     
    3334== Proposal ==
    3435
     36This proposal will modify loading metadata so that the method will do the following things:
     37
     38 * check the settings parameter hidewithheldelements if it is false then this feature is disabled
     39 * check if the current user is either an administrator or the owner of the metadata if both are false then all elements will be retrieved
     40 * search the document for the attribute: gco:nilReason='withheld'.  if the following two checks are true then all attributes (excepting gco:nilReason) will be removed, as will all child elements.  The element itself will remain as a marker
     41  * Note:  at the moment only gco:nilReason='withheld' flag an element as hidden.  In the future more tags can be added for other schema's
     42
     43By default this feature is disabled but this setting can be changed in the configuration page in administration.
     44
     45In addition to hiding the metadata the Show metadata UIs will show a message that there is hidden/censored metadata.  The most important use of this is to notify editors (that can't see the data) that they should not remove the element.
     46
     47One of the expected uses of this is to have some semantics in update-fixed-info that adds the attribute tags to the metadata when needed.  In addition a user could add the attribute via the edit UI.
     48
    3549=== Backwards Compatibility Issues ===
    3650