Changes between Version 1 and Version 2 of HiddenElements


Ignore:
Timestamp:
06/24/08 12:55:23 (17 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HiddenElements

    v1 v2  
    1 = Proposal number : Proposal title =
     1= Proposal number : Proposal title: Hidden Elements =
    22
    33|| '''Date''' || 2008/06/20 ||
    … …  
    3838'''2.''' Need an additional permissions interface to associate groups with XPaths (stage 2 – more sophisticated users)[[BR]]
    3939'''3.''' Database changes: additional dependent table on OperationAllowed – OperationAllowedElements – schema: MetadataId, Xpath – related to OperationAllowed by MetadataId and GroupId[[BR]]
    40 '''4.''' Query table and retrieve XPaths based on GroupId of UserSession, apply XPaths to JDOM tree before record returned from service – add ISO attribute (gco:nilReason=”concealed”) for ISO records only – track down all locations where this can happen – could be possible to apply this in DataManager getMetadata[[BR]]
     40'''4.''' Query table and retrieve XPaths based on GroupId of UserSession, apply XPaths to JDOM tree before record returned from service – add ISO attribute (gco:nilReason=”withheld”) for ISO records only – track down all locations where this can happen – could be possible to apply this in DataManager getMetadata[[BR]]
    4141'''5.''' Lucene index – concealed elements cannot be indexed because the index can be searched by anyone – the permissions systems is not applied until the record is displayed. The interesting outcome of leaving concealed info in the index is that a user could search and get a result on the concealed info but would not be able to see it when the record was displayed. [[BR]]
    4242