You are correct -- right now, VuFind is designed to most easily ingest data in MARC format.  While VuFind has an OAI module, it is currently incomplete (as recently discussed on this list).  I am currently in the process of changing the way VuFind deals with records to make it more easily compatible with other formats.  If you are planning on using the stable RC2 release, your best bet is to harvest the metadata, convert it to MARC format (which may well be possible with existing tools if you chain them together in the right order), and then index it in the standard VuFind fashion.  If you would like to work with newer experimental code and are willing to do some coding yourself, it might make sense to build on my current work in progress and use the OAI-DC data more directly.  For this, you would have to write an indexer to parse the OAI-DC records and send them to the Solr index (probably the hardest part) and possibly also a record driver so VuFind could appropriately display the records (if it's default index-based display was not good enough).  Again, let me know if you need more details.

 

- Demian

 

From: Reginald Amade (ext) [mailto:r.amade@vmm.be]
Sent: Monday, January 25, 2010 9:14 AM
To: Demian Katz; vufind-general@lists.sourceforge.net
Subject: RE: vufind requirements

 

Hi Demian,

 

I’m having trouble understanding how metadata harvested by the Service Provider using OAI-PMH can/must be transformed into a format that is VuFind compliant. My understanding is that the Data Provider will return metadata in oai-dc format. If this is correct then additional conversion/transformation needs to be done before VuFind can work with the data?

 

Does my understanding make any sense?

 

Thnx

Reginald

 


Van: Demian Katz [mailto:demian.katz@villanova.edu]
Verzonden: maandag 25 januari 2010 14:59
Aan: Reginald Amade (ext); vufind-general@lists.sourceforge.net
Onderwerp: RE: vufind requirements

 

VuFind was written with MySQL in mind as the back-end database, and most installations use MySQL.  However, since the database access goes through PEAR's DB_DataObject framework, it shouldn't be too difficult to adapt the code to work with a different database.  You would have to change the install process to set up the appropriate database structure in the other database system, and you would have to change the connection string in config.ini to use the appropriate format, but it might not take much more than that.

 

As for the ILS component, it is definitely not mandatory -- several existing VuFind installations are running without an ILS.  You have two options here: either edit the templates to disable functionality that won't work without an ILS (i.e. real-time availability status, some of the "My Account" pages), or write an ILS driver (as specified at http://vufind.org/wiki/building_an_ils_driver) to simulate the ILS functionality you need.

 

I'll be happy to provide more details if you still have questions.

 

- Demian

 

From: Reginald Amade (ext) [mailto:r.amade@vmm.be]
Sent: Monday, January 25, 2010 7:32 AM
To: vufind-general@lists.sourceforge.net
Subject: [VuFind-General] vufind requirements

 

Hi,

 

Can anyone tell me what type of database VuFind is compatible with and if an ILS component is mandatory?

Any suggestions or suggested reading are welcome,

 

Reginald Amade

 

 

Disclaimer: www.vmm.be/disclaimer
 
Kent u onze nieuwsbrief al? www.vmm.be/nieuwsbrief
Disclaimer: www.vmm.be/disclaimer
 
Kent u onze nieuwsbrief al? www.vmm.be/nieuwsbrief