Meaningful filenames - Revision history

Gioto: /* See also */

2011-10-08T02:34:55Z

‎See also

2011-10-08T02:34:27Z

‎What's in a name?

2011-10-08T02:33:42Z

2009-09-16T15:05:29Z

Added a possible strategy focused on Sources with multiple pages or other subunits.

2009-06-13T04:23:03Z

‎See also: wikify

2009-06-13T04:22:30Z

‎Justification: need expanding

2009-06-13T04:21:52Z

‎SWOT analysis: table

2009-06-13T04:21:07Z

fix

2009-06-13T04:20:44Z

fix

2008-12-21T05:21:03Z

‎External links: remove extra [ ]

@@ Line 267: / Line 267: @@
 = See also =
 * [[Organise your records]]
 = External links =

@@ Line 33: / Line 33: @@
   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.
+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.

← Older revision		Revision as of 02:33, 8 October 2011
Line 1:		Line 1:
	This article is about naming files in a meaningful way. Naturally files should have unique names so we don't end up with several files with the same or very similar names. This article takes file naming one step further by looking at how the file name itself can carry useful information about the file.		This article is about naming files in a meaningful way. Naturally files should have unique names so we don't end up with several files with the same or very similar names. This article takes file naming one step further by looking at how the file name itself can carry useful information about the file.
−
−	This article continues on from the article about [[Portable Filenames]] where the purpose is looking at what characters (letters, numbers and symbols) we can have in our file names, and other limits on a file naming system.

	= Why meaningful filenames =		= Why meaningful filenames =

@@ Line 254: / Line 254: @@
 * 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 =

@@ Line 256: / Line 256: @@
 = See also =
-* [[Organise_your_records]]
+* [[Organise your records]]
-* [[Portable_Filenames]]
+* [[Portable Filenames]]
 = External links =

@@ Line 177: / Line 177: @@
 == Justification ==
-Needs expanding
+{{stub}}
 == Aims ==

@@ Line 144: / Line 144: @@
 Over at Wikipedia there is a good explanation of a [http://en.wikipedia.org/wiki/SWOT_analysis SWOT analysis].
-{| border="1"
+{| {{prettytable}}
 |-
 ! Aspect

@@ Line 1: / Line 1: @@
 This article is about naming files in a meaningful way. Naturally files should have unique names so we don't end up with several files with the same or very similar names. This article takes file naming one step further by looking at how the file name itself can carry useful information about the file.
-This article continues on from the article about [[Portable_Filenames]] where the purpose is looking at what characters (letters, numbers and symbols) we can have in our file names, and other limits on a file naming system.
+This article continues on from the article about [[Portable Filenames]] where the purpose is looking at what characters (letters, numbers and symbols) we can have in our file names, and other limits on a file naming system.
 = Why meaningful filenames =

@@ Line 1: / Line 1: @@
 This article is about naming files in a meaningful way. Naturally files should have unique names so we don't end up with several files with the same or very similar names. This article takes file naming one step further by looking at how the file name itself can carry useful information about the file.
 This article continues on from the article about [[Portable_Filenames]] where the purpose is looking at what characters (letters, numbers and symbols) we can have in our file names, and other limits on a file naming system.
-== Why meaningful filenames ==
+= Why meaningful filenames =
 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:
@@ Line 270: / Line 267: @@
 * [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?]

@@ Line 263: / Line 263: @@
 = External links =
-* [[http://www.northernjourney.com/photo/articles/filenaming.html File Naming Conventions for Digitally-stored Images]]
+* [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