[ 
https://issues.apache.org/jira/browse/SIS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528705#comment-16528705
 ] 

Martin Desruisseaux commented on SIS-81:
----------------------------------------

Re-open as a side-effect of the work in {{MetadataVisitor}}. We may not provide 
an {{APPENDABLE}} enumeration, but another enumeration that may be useful could 
be {{STAGED}}. That annotation would be set by the user and treated in the same 
way than {{EDITABLE}}, except that setting a metadata to that state 
automatically set all children to that state too (if they are not {{FINAL}}), 
and modifying a staged metadata automatically put it back in {{EDITABLE}} mode. 
The intent is for allowing users to mark which metadata are ready for 
publication, pending a last review.

Note: we will probably not do that for SIS 1.0. For now, we will put only 
{{EDITABLE}} and {{FINAL}} enumeration values. But we use this JIRA task for 
recording ideas like {{STAGED}}.

> Replace ModifiableMetadata.isModifiable() by an enum
> ----------------------------------------------------
>
>                 Key: SIS-81
>                 URL: https://issues.apache.org/jira/browse/SIS-81
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Metadata
>    Affects Versions: 0.3, 0.4, 0.5, 0.6, 0.7, 0.8
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Major
>             Fix For: 1.0
>
>
> The {{ModifiableMetadata}} abstract class provides a {{isModifiable()}} 
> method which currently returns a {{boolean}} value. The boolean value should 
> be replaced by an enumeration containing the following values (for now):
> * {{EDITABLE}}
> * {{APPENDABLE}}
> * {{FINAL}}
> The new functionality is the {{APPENDABLE}} value, which would be like 
> {{EDITABLE}} except that only new values could be set; an exception would be 
> thrown on attempt to modify an existing value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to