User:Phlox/2009 05 notes

junk these
children, 1-9 spouse 1-9

==wikia requests
 * "$smwgInlineErrors = false;" so no type errors on blank fields

SMW stuff that doesn't work

 * Text input allows text values from a form that will mess up display of the page
 * The docs say the following doesn't work, so don't use examples from some sites that may use them:
 * Inverse properties, eg siblings
 * Domain and range restrictions, eg Father
 * Number restrictions and functional properties
 * Transitivity (?)
 * date type requires full date. This is lame because oftentimes we have year only, year month, or circa type dates.

Missing special pages

 * No upload ontology
 * no upload vocabulary

Wierd/ anomalous stuff

 * returns lots of pages. Does it recognize pagename as a key word? or is it undefined when first operand is null?
 * form weird syntax:  in page http://discoursedb.org/w/index.php?title=Form:Author&action=edit
 * "author" is the feeding template name for the form, and first name/ last name are parameters from it.

Cool stuff

 * Timeline output (for all subprops of event date)

Complex types

 * Marriage eg. Edward Riggs (1589)/Holmes-Riggs
 * residences (big because of censuses)
 * All other events with multiples: Occupations, Education
 * Migration event emigration: (from country, ship, ports), moving: mode of transport, reason, motivation
 * Citations? whoa.  That certainly is complex, but will the user have to create a separate page for every one of these jokers?

Small pages
Something goes against the grain about having all these tiny pages sitting around. The tough thing about these events naming them.
 * 1) They aren't owned by one person- eg the husband. What if it turns out that the name of the person gets changed etc. Do they then have to move 20 of these bittey pages every time they rename?  Hmmm.  Maybe a bot can do this.  And who owns them?  Does the Husband own the marriage event or the wife?  If the naming uses both people's names aren't you just doubling the chances of move due to a changed birth or death date?  OK, maybe these events are owned by one of the parties- doesn't matter who- it's just a unique name.

Implementation

 * Opening via form on redlink- To property "occupation"(s), add value has default form.
 * ??pagename should be a subpage, but user has entered the page name. So they could muck it up. OK.  Maybe they enter a string, then save the form.  On next form load, the template doesn't display the string, and instead creates the real field of type Page, decorating it with the proper prefix.
 * Note that for shared events like marriage or migration, say the husband already created a marriage page. Wife needs to poll the husband to see if a page already exists and link to that first.
 * Maybe there is a smarter form way of doing this.

Pro/Con

 * Pro1: Removes a tremendous amount of clutter from main page.
 * Pro2: Tidies the Property namespace (no occupation8-locality, etc.)
 * Con1:This could potentially disrupt workflow. You have to open a new page to type in marriage info.


 * Conclusion1: Being a subpage doesn't imply anything. It has to go somewhere, and being top level means it will collide with other similar names.  So keep these complex types as a subpage, use some logical naming convention, and call if folks want to get fancier later, they may do so.

Tips

 * Subproperties means you can search for groups. EG if birth date, death date, marriage date are all subprops of event date, then searching on event date picks up hits on all of them.
 * Forms have a preload option
 * There are a set and declare statements:

Potential case studies

 * Family tree projects
 * - Trout