NTS:: Some ideas for a Windows-friendly approach for basic indexing of OAI-PMH content (amongst other sources).

Thinking about my brief flirtation with an EAV variant, I've realised that I should probably stick with a traditional structure, (and possibly use views to produce the output I would like).

1. Grab OAI-PMH content


2. For each record from OAI source, store it in Postgres (temp table? - alternatively use a table for each OAI source)


3. Create Postgres indices/tables from xpath queries... a standard xpath query wouldn't work with all OAI sources, (some include non Dublin Core content such as DIDL)
   


4. Run Sphinx over select Postgres tables


5. (Empty the Postgres temp table?)

Then can use Sphinx for other sources as well...

NTS:: RDA (Important Library Stuff)

Hmmm... it did look like RDA might be the sort of thing I was wanting... supposed to have the granularity I'd like, but just seeing the draft documents makes me just balk.

Once you download the zip file, and see the size of the pdfs, you realise how much work has been done, (a lot), but also how much work is involved in implementing it. Not being a cataloguer, getting my head around this would take too long, so I'm probably going to soften it, and go with something similar, but easier.

My grand plan, (which is all it is at this stage - whether it gets to be anything more is dubious), would be a central repository for the tags, and how they translate... whether this would be a networked thing remains to be seen.

NTS:: Database structure and "flattened MaRC"

Thinking about how MaRC works, makes me think that subject (record?), property, value is not enough... or maybe I've not caught on to RDF just yet?

Column structure for a simple database (along the lines of XML and a flattened MaRC structure):

(okay, so this is not going to set the world on fire, but I think it's useable)

ROW # (autoincrement) | RECORD | LINE | ORDER | VALUE
1 | 1 | creator:surname | 001 | Smith
2 | 1 | creator:firstname | 001 | James
3 | 1 | title:entire | 001 | MySQL : Exploring database design
4 | 1 | published:date | 001 | 2004
5 | 1 | published:edition | 001 | [1st]
6 | 1 | published:date | 002 | 2006
7 | 1 | published:edition | 002 | 2nd