[greenstone-devel] a simple patch to allow collection builders to assign a documentidentifier (OID)

From Stephen.DeGabrielle@ntu.edu.au
DateMon, 21 Jul 2003 16:37:30 +0930
Subject [greenstone-devel] a simple patch to allow collection builders to assign a documentidentifier (OID)
Hi,

We needed the ability to assign our own unique identifiers to greenstone
documents- in our case the 'Hash' and 'Incremental' methods of assigning
identifiers were not suitable as we would like greenstone to use the
identifiers created by our others systems.

We have put together a simple patch to allow an new value for the -OIDtype
flag when using import.pl

to call it simply type;
import.pl -OIDtype barcode -removeold ntlier
and include a <Metadata name="Barcode">C10001</Metadata> for each document

We can send a zip file to anyone who wants a look. It consists of adding
code to looks for and accept the barcode flag and retrieve it from the
document metadata (look for a long ########### to find where we made
changes)

If this is OK with the developers could this facility be added to the
greenstone distribution? We are keen not to branch away.

One problem; we have included our 'Barcode' metadat in the default index,
but when we tried to search it weirdly split search term "C10001":
>Word count: C1000: 2, 1: 13
>2 documents matched the query.
We used the double quotes but it still split the term into 'C1000' and '1'.
Any ideas what went wrong here? Does MG have problems with large numbers or
other nontext characters?
(It didn't happen when we changed our Barcode metadata field values to
'1ntu','2ntu'!)

Regards

Stephen & Iwona
_________________________________________________
Stephen De Gabrielle
Digitisation Officer
AraDA Project