Difference between revisions of "Term"
(→Reader Management) |
(→Field) |
||
| Line 1: | Line 1: | ||
''Note for editors - please try to keep this in roughly alphabetical order'' | ''Note for editors - please try to keep this in roughly alphabetical order'' | ||
== Field == | == Field == | ||
| + | '''''Field''''' has a broad meaning in ActionApps and the word is used in several different contexts. A set of ''fields'' creates what we call a ''''slice structure''''. An example could be a news slice - we certainly will have one separate ''field'' for the headline. So, ''field'' is a "box" which holds a value/information about a particular aspect of the item (in this case, it holds the headline). | ||
| + | |||
| + | In database language, ''field'' would be a ''table column''. | ||
| + | |||
| + | ''Field'' is not just an abstract division of ''slice'' to for the ''slice structure''. It manifests itself in several other ways. Usualy there is some ''user control'' (i.e. a textbox) attached to it to allow the user to fill in the data (i.e. the headline), validation function to check for the validity of the user input. There will also possibly be an alias or a {} expression attached to each field to read it's content. | ||
| + | |||
| + | [[Image:field_headline1.png]] | ||
| + | |||
| + | [[Image:field_headline2.png]] | ||
| + | |||
| + | Read more about fields in [[Planning Your Data Model and Taxonomies]]. | ||
| + | |||
== Item == | == Item == | ||
== Parameter == | == Parameter == | ||
Revision as of 14:12, 13 August 2005
Note for editors - please try to keep this in roughly alphabetical order
Contents
Field
Field has a broad meaning in ActionApps and the word is used in several different contexts. A set of fields creates what we call a 'slice structure'. An example could be a news slice - we certainly will have one separate field for the headline. So, field is a "box" which holds a value/information about a particular aspect of the item (in this case, it holds the headline).
In database language, field would be a table column.
Field is not just an abstract division of slice to for the slice structure. It manifests itself in several other ways. Usualy there is some user control (i.e. a textbox) attached to it to allow the user to fill in the data (i.e. the headline), validation function to check for the validity of the user input. There will also possibly be an alias or a {} expression attached to each field to read it's content.
Read more about fields in Planning Your Data Model and Taxonomies.
Item
Parameter
Reader Management
What is Reader Management?
Reader Management is a special kind of slice that is designed to contain data about subscribed "readers" (aka public web site users). A Reader Management slice can be used to send automated email alerts of new AA items, personalize page views, send bulk target emails, and generally act as a contact database. Anonymous forms can be set-up to allow users to change their subscriptions and contact data in the Reader slice.
Slice
What is slice?. If you know databases (relational databases), the answer is simple. Slice is a database table. If you don't, don't worry. It's simple.
We use the term "slice", because we like to look at one ActionApps installation as one big pie, and each user can have a bite ( or slice ). The pie is made of items, which are particulary tasty, and each item belongs to one slice. So, another way to look at this is that slice is a container (basket) full of items.
There is more to slice:
~ToDo: insert picture explaining slice
Slice can or can't be accessed by ActionApps User depending on the User Permissions Slice can generate parts of web pages Views depending on the actual content in it, and it can even look nice if you have spend some time playing around with the Design Templates.
The way you set your slice up will be reflected in many other areas, becuase it not only holds content, but Slice Settings also determine the look of Item Manager, data structure and Input Controls .
Moreover, slices can be created, modified, deleted, exported to another ActionApps installation, imported from somewhere, synchronized across several ActionApps installations, and last but not least, blamed for things not working the way they should.
Some useful links realated to slice topics:
~ToDo: link to the relevant slice documentation
