Apologies, I should have used Plain English for an international audience. 'Sundry' means 'miscellaneous' or 'other'
Ideally for each person, I'd generate a range of date for mentions, a check to see whether they had obituaries in the index, I'll also generate URLs into the search engines for various external systems (worldcat, VIAF, ORCID, digitalnz, etc) because these are useful to the editor who makes the decisions about using the content to make the wikipedia stub.
I have a new phone number: 04 463 5692
From: Code for Libraries <[log in to unmask]> on behalf of Jean-Claude Dauphin <[log in to unmask]>
Sent: Tuesday, 4 November 2014 7:40 a.m.
To: [log in to unmask]
Subject: Re: [CODE4LIB] MARC reporting engine
I made some experiments with the innz-metadata in J-ISIS software, and you
may be interested to read the summary which is attached. Thank you for
informing the CODE4LIB list about the innz-metadata dataset, this is very
useful for testing and improving J-ISIS.
But now, I would like to see if it's easy to do what you wish to achieve
with J-ISIS. Please excuse my ignorance, but could you please explain on
which MARC fields or subfields you wish to extract the person authorities
and explain me what are the sundry metadata and how they are related to
MARC records. I googled about "sundry metadata" but didn't found any
On Mon, Nov 3, 2014 at 4:24 PM, Brian Kennison <[log in to unmask]> wrote:
> On Nov 2, 2014, at 9:29 PM, Stuart Yeates <[log in to unmask]<mailto:
> [log in to unmask]>> wrote:
> Do any of these have built-in indexing? 800k records isn't going to fit in
> memory and if building my own MARC indexer is 'relatively straightforward'
> then you're a better coder than I am.
> I think the XMLDB idea is the way to go but I’d use Basex (
> http://basex.org). Basex has query and indexing capabilities, If you
> know XSLT (and SQL) then you’d at least have a start with Xquery.
[log in to unmask]
[log in to unmask]