After thinking about the limits to how we can structure our files and folder (see [[Portable_Filenames]]) the next step is developing a semantic controlled vocabulary.
Before launching too deep into this lets look at what we want to achieve.* Understandable filenames* Computer readable filenames* A system simple enough to remember
To be understandable we need to be able to use full words where appropriate.
To be computer readable we need to
seperate the parts in a way which a script can easily recognise and, more importantly, in a way which would never occur in real language. So it would be no good to mark a ''name'' section with the word ''name'' if we also can use the word name somewhere in the file where it is not meant to be a marker.
To be simple enough to remember the system should not be too complicated, after all
GRAMPS is meant to store the real information, this is just a supplement.
== What's in a name? ==
It would be nice if we could have files called
Marriage of Mary Angus Jones and Matthew Williams, 2nd Dec 1923 (William Angus is to Mary's right).jpg
But this meets only one of the criteria above, that of ''understandable filenames''. How can a computer know who got married? what their surnames are? and so on. And anyway because of the limitations of
[[Portable_Filenames]] we can't have file names like that. We have to drop the reliance on capitalisation, drop the spaces, drop the comma and drop the brackets. To be computer readable we need to separate the sections with a system of markers to indicate where the surname, event name etc are.
So what sections do we want to be able to identify? Here's a basic list that should be enough for most situation, remember that
GRAMPS stores the more complex information, we're just trying to give a useful structure to our files.
== Source events ==
The GEDCOM 5.5 standard defines so few events as to be useless. The
GRAMPS XML schema defines no events as these can be made by the user. This all seems fair enough since events are highly culture based. The situations where I think a set of events should be defined are those which will be connected with source records. GEDCOM has a reasonable group of those but they are heavily based in western christian culture. The solution must be language and culture dependent. Here's my list:
'''marriage''' is for an actual marriage event and all the associated documentation, including possible divorce and separation documentation.
This could be parsed (by
GRAMPS?) as the description:
This could be parsed (by
GRAMPS?) as the description:
Over at Wikipedia there is a good explanation of a [http://en.wikipedia.org/wiki/SWOT_analysis SWOT analysis].
GRAMPS ID based = This is another attempt by [[User:Duncan|Duncan Lithgow]] to find a good system. It is not finshed so feel free to add comments and correct any obvious mistakes.
== Record types ==
GRAMPS ID's use the first character to denote the type of item the ID refers to. Taking the most relevant ones these can be converted to the following tags:
'''I-- ''' Individual* '''P-- ''' Place* '''E-- ''' Event* ''' S--''' Source
== Record properties ==
By making all properties of each record compulsory we avoid extra tags like ''GN'' for given name and so on. We can what a property is by where it is in the file name.
* ''' family name ''' is their surname before marriage, but including deed pool changes, MacArthur for example* '''given name ''' is their official first name* '''uid ''' is a unique identity, in this example the (original) GRAMPS ID of the media file* '''source date ''' is the date in ISO 8601 format when the information left the people or organisation responsible for it* '''event date ''' is the date in ISO 8601 format when the event occured or started. YYYY-MM-DD, ie. ''2008-12-28 ''* '''event type ''' is a noun describing the event, chosen from a list of event types, ie: ''marriage ''* '''title ''' is the name of a document (book, letter, census) or object (gravestone, heirloom), ie. ''williams__arthur_headstone ''* '''source author name ''' is the name of the person or organisation most responsible for the information. For people always use family name first followed by two underscores (__), ie: ''church_of_lds ''* '''note ''' is for notes. Names should always be family name first followed by a double underscore
== Naming structure ==
Putting it all together
* File names start with a single capital letter representing their record type.
* Record properties are separated by two dashes
/ minus signs (--). Two dashes/ minus signs (--) can not be used for anything else.
* Missing information is replaced by a single underscore (_).
* Names in notes should always be family name first and separated by two underscores, ie: ''doe__john'' which can be represented as ''John Doe'' or ''Doe, John''.
* Place names should start with the largest geographical region followed by a double underscore before the next geographical region, ie: ''oz__far_far_away__yellow_brick_road'' which can be represented as ''Oz, Far far away, Yellow brick road''.
'''Individual''' I--<family name>--<given name>--<note>--<uid>.ext * Example: ''I--williams--mary_agnes--portrait_sketch--o3472.jpg''
'''Place''' <nowiki>P--<place__sub place__sub sub place>--<note>--<uid>. ext</nowiki> * Example: ''P--united_kingdom__england__london--williams__mary_agnes_house--o0857. jpg''
'''Event''' E- -<event ISO date>--<event type>--<1st family name >-- <2nd family name>-- <3rd family name >--<4th family name>--<note>--<uid>.ext * Example: ''E--1923-12-02--marriage--jones--williams--_--_--william__angus_to_right_of_mary--o2846. jpg''
'Source ' '' S-- <title>-- <source author name >--<source ISO date>--<note>--<uid>. ext * Example: '' S--census__uk__london__engelfield--1840-03-2--jones__mary_jean_at_johns_road--o0847. pdf'' * Example: ''S-- jones_family_from_1735--dean__angus--1972-06-21--shows_connection_to_dean_family--o5689. pdf''
= See also =
Organise_your_records]]* [ [Portable_Filenames]]
= External links =
[[http://www.northernjourney.com/photo/articles/filenaming.html File Naming Conventions for Digitally-stored Images ]]
* [http://en.wikipedia.org/wiki/Metadata Metadata] at Wikipedia - data about data
* [http://en.wikipedia.org/wiki/Meta_tags Meta tags] at Wikipedia
* [http://www.43folders.com/2006/10/23/file-naming?page=2 File naming] at 43folder.com
* [http://whatdoiknow.org/archives/000442.shtml File Naming / Organization Methods?] from [http://whatdoiknow.org What do I know?]