On 10.10.2013 11:18, Henning Hraban Ramm wrote:

Hi!

Now, I got some questions on how to proceed - I’m missing "Setup" documentation between 
"Installation" and "Administration".

* How do I get rid of the demo data?

inveniocfg --remove-demo-records
inveniocfg --drop-demo-site

cf. inveniocfg --help

Should I just delete the database and install anew or is there a better way?

This works. You could then just leave out loading them.

What we actually did when we started out was to write a
bash-script that does all necessary steps in sequence, so we
could just delete everything all the time and be at a
workign point 0 in a couple of minutes.

* I’ll get my metadata in Excel files.

Urgh. Either you have totally simple stuff (only books that
all have an author and never an issuing institution and so
on) or you might end up in trouble. At least xls is not
suitable for /real/ bibliographic data. Think of several
authors, differences in fields by document type and stuff.

As far as I understand BibConvert docs, there seems no way
to process CSV files directly.

It is just not suitable for bibliographic data ;) How do you
map a repeatable field? The simplest one that comes to mind
are authors.

(BibTeX or friends are not an option? Would at least handle
the simple specialities correctly. Editing via Jabref e.g.
is quite easy...)

Is that right or can you hint me on a sample? Otherwise
I’d write some Python script to convert our tables to MARC
XML - or would you go via some other text format to
convert via BibConvert?

MarcXML is perfect for this. I'd also resort to python in
this case as it might be more flexible in the end anyway. We
also droped bibconvert in our websubmit workflow and
resorted to python there as well as it is easier to handle
these, did I mention, specialities? ;)

Basically, you could write websubmit-style functions for
this and later on hook up with websubmit if needs be. Or
check out next/-branch and webdeposit trying to be
compatible with that from the start.

* I guess I still don’t understand some basic concepts of
Invenio, e.g. what modules and stuff I must set up all in
all - I was playing with WebSubmit and trying to set up
all the fields that we need, but since we’ll batch upload,
I don’t know if that makes sense at all.

Depends. If you can load parts of your data to websubmit and
then pass it on to invenio it might help to get better data.
We do this semiautomatic ingesting for e.g. journal articles
via DIO, books via ISBN and stuff like that.

So, if we got MARC XML (via BibConvert or my own script),
do I need to setup any field mappings or the like?

You could probably ignore it there. However I'm not sure
that your xls ingest is a good idea if you have several
document types etc. Might be that you end up in having some
sort of websubmit in the end or at least the wish to have it
for corrections. Depending on complexity websubmit could be
easier to handle than direct bibedit. (Innerrecordlinking in
bibedit is a bit pita, complex structured fields require
some work.)

BTW: The upcoming Invenio User Group meeting might be of
interest to you.

http://indico.cern.ch/conferenceDisplay.py?confId=258575

--

Kind regards,

Alexander Wagner
Subject Specialist
Central Library
52425 Juelich

mail : [email protected]
phone: +49 2461 61-1586
Fax  : +49 2461 61-6103
www.fz-juelich.de/zb/DE/zb-fi


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to