Structuring your Memento Database: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
mNo edit summary
mNo edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Stamp|2016-09-27|3.9.7|1.0.3}}
{{Stamp|2016-09-27|3.9.7|1.0.3}}


'''''[[This page is in its infancy, is incorrect, incomplete, and under development.]]'''''
'''''[[This page is incorrect, incomplete, and under development.]]'''''


If you're just starting with Memento or just starting to use it for something new, it may not be clear to you how to represent your data in Memento to allow the user to get what he/she wants out of it. This article suggests some approaches to consider.
If you're just starting with Memento or just starting to use it for something new, it may not be clear to you how to represent your data in Memento to allow the user to get what he/she wants out of it. This article suggests some approaches to consider.


== Structuring simply — One Main Thing ==
== Structuring simply — One Main Thing ==
The simplest use of Memento is to use a single library to represent data about a single thing.
The simplest use of Memento is to use a single library to represent data about a single subject.


=== Simple uses ===
=== Simple uses ===
For instance, you might want to have a To Do list in Memento. As is often the case, it could be anywhere from very simple to pretty complex. Let's start with the very simplest one, so see '''[[Tutorial:Simple To Do List]]'''.
For instance, you might want to have a To Do list in Memento. As is often the case, it could be anywhere from very simple to pretty complex. Let's start with the very simplest one, so see '''[[Tutorial:Simple To Do List]]'''.


Another simple use would be as a library of recipes. Could you use Memento in a very simple way to catalog your recipes and then look them up later? The easy answer is <big>'''yes'''</big>. See '''[[Tutorial:Simple Recipes]]'''.
Another simple use would be as a library of recipes. Could you use Memento in a very simple way to catalog your recipes and then look them up later? The easy answer is '''yes'''. See '''[[Tutorial:Simple Recipes]]'''.


The key to simplicity is that all information in this library is '''about the task or recipe as a whole'''. These simple solutions don't try to define details of ingredients, nutrition, task duration, or due dates &mdash; just the Tasks and the Recipes themselves.
The key to simplicity is that all information in each library is '''about the task or recipe as a whole'''. These simple solutions don't try to define details of ingredients, nutrition, projects, or deliverables &mdash; just the Tasks and the Recipes themselves.


=== Pages of simple data ===
=== Pages of simple data ===
Line 25: Line 25:
* They remind the user of the possible values of the field.
* They remind the user of the possible values of the field.
* They prevent typos from inadvertently cluttering the library.
* They prevent typos from inadvertently cluttering the library.
What lists do not do is define another level of data structure. Other than list item indentifiers, no further data is introduced. To introduce more data about list items, create a new library for those items and replace the list field with a link to the new library; you have now added an extra level of complexity, but you've also expanded the coverage of your database. So long as each library focuses on a single subject, the increase in complexity will only match the increase in subject matter; it will not outstrip it.


=== Using special data ===
=== Using special data ===
Line 58: Line 60:
==== One library per subject that contains dependent data ====
==== One library per subject that contains dependent data ====


=== Slicing & dicing when using multiple libraries ===
=== Structuring for data analysis &mdash; slicing & dicing ===


== Structuring &mdash; Serious slicing & dicing ==
== Structuring &mdash; Enhancing your visual presentation ==
== Structuring &mdash; Enhancing your visual presentation ==
=== Fields sharing a row ===
=== Fields sharing a card row ===
=== Field fonts & colors ===
=== Field fonts & colors ===
=== List items with fonts, colors, and icons ===
=== List items with fonts, colors, and icons ===
=== Using images ===
=== Using images ===
=== Charting your data ===
 
== Structuring &mdash; Leveraging the Internet ==
== Structuring &mdash; Leveraging the Internet ==
=== Using Autofill ===
=== Using Autofill ===
=== Using barcodes ===
=== Using barcodes ===
-----
-----
-----
-----
; the casual, perhaps single-library user : who just wants to throw up a grocery list or recipe repository
; the casual, perhaps single-library user : who just wants to throw up a grocery list or recipe repository
; the intermediate user : who might want to have some related libraries tracking some activities
; the intermediate user : who might want to have some related libraries tracking some activities

Navigation menu