EDIT

{{>toc}}

# Editor Strategies

Handling protected cache fields and atomized data, freetext areas and structure data input, objects that need to be updated but are related to other objcets, and other issues at the same time needs defined stratagies.

This page tries to point out the different strategies and to lay emphasis on the possible alternatives and considered rules.

## Strategies

Strategies to be considere are

1. Interaction of cache / atomized fields and protected /non protected states

1. Locking freetext area

1. Object change strategy

1. NameRelationships: Editing (in particular basionyms and replaced synonyms, parsing of homonyms)

## Interaction of cache / atomized fields and protected /non protected states

to be done

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

Just some text to move this all down

## Locking freetext area

### Attributes that will lead to a lock independent of the object change strategy

|Attribute| Reasoning |Example(s)|Actions needed| Notes |

|name.appendedPhrase|a change in name.appededPhrase is shown in the fullTitleCache and therefore in the freetext, but name.appended phrase can not be parsed  |  | |  |

|NOT: taxon.appendedPhrase| a change in taxon.appededPhrase is not shown in the freetext area| | | | |

|All protected caches like | a change in one of the cache fields is reflected in the fullTitleCache and the freetext. Generally the parser may not be able to set the same protected caches as the details view (either it may unprotect parts that are protected on purpose or more often it will protect other caches that do not need to be protected  | _Areca calisoA Becc., Leafl. Philipp. Bot.  8: 2998 (1919)_ may have a protected namecache because the name part is not parsable. Ones you edit this in the freetext the whole string will not be parsable resulting in a protected full title cache  | | |

|name.fullTitleCache |  |  | | |

|name.titleCache |  |  | | |

|name.nameCache|  |  | |  |

|name.authorshipCache|  |  | | |

|name.combinationAuthorTeam.nomenclaturalCache (and other teams)|  |  | | |

### Attributes that will lead to a lock dependent of the object change strategy

* to be done

## Object Change Strategy

Object change stragies may have two extremes. The first resulting in almost no new objects when you change any data. The second resulting in only new objects with even objects created new because they relate to a changed object, e.g. a TaxonName may be created new because its nomenclatural reference has been changed.

In the following these two strategies are described and some rules are destilled from this