no edit summary
If all names are kept unique why also try to embed meaning in the file name itself? Here are some approaches to managing information about information which which you might recognise:
* Data about data (called ''metadata'', ([http://en.wikipedia.org/wiki/Metadata Wikipedia's ''Metadata'' entry]) can also be stored inside the file it describes, for example:
** HTML, the language of webpages, uses tags like ''<span style="normalText">Example</span>''. Here the meta data describes the style of the text, ie: ''Example'' is ''normalText''
** EXIF ([http://en.wikipedia.org/wiki/Exchangeable_image_file_format Wikipedia's ''EXIF'' entry]) is a way of storing meta data in image files, like when the photo was taken and what type of camera was used* Database systems (
GRAMPS is a database system for genealogy) can store a huge amount of data about data. They 're are very efficient at this job and very powerful.** Google Search uses a database to remember what web pages are about, and tells you when you ask
So why not use one of those options?
* EXIF is great, but only for some types of files, there are lots of different systems for different types of files. People are working hard to improve this situation all the time.
* HTML is great if you can store all your information as HTML files, but HTML files cannot contain other files, they just point to them. So we'd basically end up making a website about our files.
* A database, well we already use this when we use
GRAMPS. The GRAMPS database stores lots of information about the files and records it records. But GRAMPS does not store the actual file inside the database. If the connection between GRAMPS and the data it is describing is broken, then the files are just files. They contain no more information than they did when you first ''imported'' them into GRAMPS.
This system of ''meaningful filenames'' has the following aims:
* Preserving enough metadata to give the file's content context without
GRAMPS* Creating file names normal people can understand so they can see what the file is about without GRAMPS
* Creating file names which a computer can process easily so files need to be batch processed and metadata can be read directly from the file name without possible confusion
* Creating a system simple enough to use all the time for every file
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? ==
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.
Here's the records we'll use as examples. They involve Mary Agnes Williams (daughter of John Williams and Anna Matthews). She married Anders Sørensen (son of Anders Sørensen and Anna ?) and they had a daughter Anna Sorensen, note the spelling change.
== Justification ==
== Aims ==
== Record types ==
The record types tell us what the record is about.
GRAMPS ID's use the first character to denote the type of item the ID refers to. Sticking to something already thought and taking the most relevant ones to stored records these can be used as the following tags for record types:
* I-- Individual
* 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
Here's a version of the naming structure for quick reference.
== Examples ==
* Marriage certificate: ''S--marriage_certificate--jensen__williams--anders__mary_agnes--uk__london--1823-12-02--_--00864.pdf''
* Portrait: ''I--portrait--williams--mary_agnes--uk__london--1823-12-03--wedding_portrait--000967.jpg''
= 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?]