Hi, thank you for your answer! Am 2013-10-10 um 16:42 schrieb Alexander Wagner <[email protected]>:
>> * How do I get rid of the demo data? > > inveniocfg --remove-demo-records > inveniocfg --drop-demo-site > > cf. inveniocfg --help Oh yes, I remember I saw that anywhere… Works. >> * 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. Yes, we’ll mostly have really simple stuff. I'm glad if we get metadata at all for the heap of media, e.g. hundreds of little educational films without author, year, location etc. but just a publishing organization and some keywords for search (and a hint of taxonomy). Or a bunch of public domain eBooks (just author and title, no hint about which edition was used etc.). Several authors are easy: Last1, First1 Middle1; Last2, First2; Last3, First3 Fathersname3 I get different media/document types in different tables, the differences are marginal (e.g. number of pages vs. length in minutes), and I can handle them in my script. > (BibTeX or friends are not an option? Would at least handle > the simple specialities correctly. Editing via Jabref e.g. > is quite easy…) The staff only knows "standard" office applications; I bother the translators to use POedit, but won't try to convince anyone to use some other program that I never used ;-) > 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. Thanks. >> * 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. Ok. Of course we need to be able to update data after uploading. >> 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.) I'll still have to find out how to… - translate/alias keywords or taxonomy (we need to find media independent of language) - cope with media that consists of several files (e.g. audio book chapters) > BTW: The upcoming Invenio User Group meeting might be of > interest to you. > http://indico.cern.ch/conferenceDisplay.py?confId=258575 Would be nice, but I'm sitting in Kyrgyzstan for the time being… Best regards, Hraban http://www.fiee.net
