<commit_before>Monitoring Features Functional Design
-------------------------------------

### Documents
Github issues:
https://github.com/akvo/akvo-flow/issues/276
https://github.com/akvo/akvo-flow-mobile/issues/32

### Overview
Monitoring features will enabe users to download data on existing points on their phones, and add information to these points This feature introduces the concept of a 'monitored entity', which has a identity and can be tracked over time. Multiple different surveys can contribute data to a single entity.

This can be visualised by comparing it with record files containing paper forms: one of the forms creates the record file, and other forms can be added to the record file. A special form may also exist which archives or closes the record file. The enumerator has access to a certain set of record files, including the forms contained in them.

### Marketing description
**Track things over time with the new FLOW Monitoring Feature**

Taking a survey of something, be it a water point, a person, or a school, is usually a one-time thing. You collect data, analyse the data, take action, and that's it. But in many cases, you also want to go back at a later date, and do a follow-up: is this pump still working? Has the income of this person changed? Has that schools' latrine been repaired? This is what we call monitoring: observing the progress of quality of something, some 'entity', over a period of time.

Using the new *Monitoring features* enables Akvo FLOW users to do this. Regular survey forms can be used to register entities, so they can be retrieved later for further data collection. FLOW users can download existing entities to their phones, and add information using additional survey forms. This makes it possible to see how data has changed over time, or to collect new properties of the same entity.
<commit_msg>Issue #1 - change marketing text<commit_after>Monitoring Features Functional Design
-------------------------------------

### Documents
Github issues:
https://github.com/akvo/akvo-flow/issues/276
https://github.com/akvo/akvo-flow-mobile/issues/32

### Overview
Monitoring features will enabe users to download data on existing points on their phones, and add information to these points This feature introduces the concept of a 'monitored entity', which has a identity and can be tracked over time. Multiple different surveys can contribute data to a single entity.

This can be visualised by comparing it with record files containing paper forms: one of the forms creates the record file, and other forms can be added to the record file. A special form may also exist which archives or closes the record file. The enumerator has access to a certain set of record files, including the forms contained in them.

### Marketing description
**Track things over time with the new FLOW Monitoring Feature**

Taking a survey of something, be it a water point, a tree, or a school, is usually a one-time thing. You collect data, analyse the data, take action, and that's it. But in many cases, you also want to go back at a later date, and do a follow-up: is this pump still working? Has the tree grown? Has that schools' latrine been repaired? This is what we call monitoring: observing the progress of quality of something, some 'entity', over a period of time.

Using the new *Monitoring features* enables Akvo FLOW users to do this. Regular survey forms can be used to register entities, so they can be retrieved later for further data collection. FLOW users can download existing entities to their phones, and add information using additional survey forms. This makes it possible to see how data has changed over time, or to collect new properties of the same entity.

{'fraction_non_alphanumeric': 0.06427423674343867, 'fraction_numerical': 0.0029459025174076057, 'mean_word_length': 4.0885558583106265, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1892386', 'n_tokens_mistral': 873, 'n_tokens_neox': 831, 'n_words': 575}