eBook File Names, Any Rational Constructions? - Squink, Inky A. (ed)

Factual Questions
1

It being 2010, I’ve a modest collection of eBooks on my computer/iPad.
Coming from a variety of sources, they are also named in a variety of of different styles:

Title, Authorfirst Authorlast
Title - Authorfirst Authorlast
Authorfirst Authorlast - Title
Authorlast Authorfirst - Title
Authorlast, Authorfirst - Title
Title Only
Random unintelligible garbage with some sort of code # in it, and lots of _'s and '##'s

To say nothing of short story marks (SS), (ed) or (eds), multiple authors (, and ampersand et. al.), genre (technical, SF, mystery, history, sciences, poesy…) etc. etc. etc.

The situation is manageable at present. I can find the books I want. But I expect that’ll change over the next decade as I accumulate more of the things.
Are there any published conventions for naming these files in a consistent, intelligible and searchable fashion?
Free ISBN lookup sites?

I’m almost tempted to write a little book file packager that lets me bundle an electronic catalog card with each file, regardless of the text’s actual format,
But that’s not going to be very portable.
I know the epub format is drifting in a similar direction, but is anyone ever going take the bit in their mouth and pull?
On a related note, which ebook formats are likely to have a future, and which are fossils that I should extract my text from, while the utilities to do so still run on current hardware?

Finally, has the computer age killed off the post fixing of ‘the’ in titles, eg (Anubis Gates, The - Powers, Tim)?
Seems to me, the demise of paper catalog cards sort of killed the reason for this convention. Is there some reason for it besides making physical searches easier?

2

Oh look, I sent a mod message to move this thread, THEN I read your ‘reason for editing’. Doh.

Nothing to add to your OP. I don’t have your problem yet, not having any ebooks or ebook readers. But I look forward to having to grapple with it in the next couple of years - my music files have already given me many hours of merriment writing perl scripts to automate their mp3ing, and logical database schemas to cover their properties. :slight_smile:

3

Moved from Pit to GQ.

4

Forget filenames. This is what metadata is for. MP3 has it in the form of ID3 tags and different eBook formats will have their own schemes.

If you’re not pirating content, most purchased digital files will have metadata already. If you need to add them and have an ISBN, a simple Amazon or Google Books search will give you the relevant info. There are probably APIs for both if you want to do it programatically for many books.

5

Keyword being most.
With so many different formats, there’s little consistency. Even .epub lacks a proper standard for how cover images should be stored and named. Plus with metadata, I need a specialized bit of software to extract and read the info. As mentioned, I could roll my own container, but still I think it’s preferable to load as much user intelligible data into filenames as is practical.

Anyone else have comments?