Hi again!

Today I had a meeting with my manager, and we decided to use a simple plain 
text input format (instead Excel/CSV) that should be convertible with 
BibConvert, e.g.:

        FILE    Literature/Educational/16527.epub
        CAT     Educational;Math
        TITLE   1001 задача для умственного счета       
        AUT     Rachinskij, Sergej Aleksandrovich
        DESC    A collection of mathematical puzzles    
        LANG    rus     
        YEAR    1899    
        PUBL    Project Gutenberg
        SRC     gutenberg.org
        LIC     Project Gutenberg License
        REFNO   16527
        KEY     sadanye
        KEY     puzzle

Most key codes can appear several times, and we defined some more codes than 
shown here. (Of course most contents will be in Russian, but I wrote my 
documentation and samples in English.) 


Am 2013-10-11 um 13:22 schrieb Alexander Wagner <[email protected]>:

>> [WebSubmit is] good for later additions.
> 
> What I wanted to point out is a "lessons learned" from
> our project. We went a similar way as you, writing a python
> file to ingest some format and then developed websubmit for
> later manual additions. In retrospective I would do it the
> other way round: first develop the websubmit and then use
> the functions we needed there anyway for the initial batch
> ingestion. It's not a real deal breaker the way we did it as
> we deliberatly disabled(!) web-modify for converted records,
> ie. we decided that old records get modifications by bibedit
> only, but in some places even if you have librarians for
> this it would come in handy to use the logic of our (well
> quite complex) websubmit.

I imagine exporting the same format again, with Invenio IDs added, and insert 
modifications that way.
But I still don’t know Invenio enough to be able to tell if that makes sense...

>> We just need translatable "tags", so that someone looking
>> for "dog" also finds media tagged with "hund" and "chien".
> 
> Probably you can use some existing vocabulary with
> translations? LoC e.g. has linkate to German, I don't know
> something the like in your languages as I know neither of
> those languages but I can imagine that there's something
> available as the USSR seemd to have a quite good library
> system.

My problem is not to find a vocabulary with translations but to understand how 
to handle keyword synonyms/translations in Invenio.

>> Can you hint me on the docs about setting up a
>> (translatable?) taxonomy tree or similar structure?

[…]

Thank you very much, that’s a lot to read. I’ll call back.

> For a unified search you'd like to have I think at least
> Invenio 1.2 (current head master, if Tibor managed to merge
> authority based searches yet).

Grmbl, I forked at v1.1.2.473-1ab71 and decoupled. But I must learn how to 
manage upstream changes in git anyway. At the moment, I set my personal server 
repository as origin, develop on my Mac and pull changes from the development 
web server. All my changes (e.g. configuration, web style, docs) are in a 
personal branch, so it should cause no problems to pull master.

>> Is that what "collections" are about?
> 
> Nope. What's closest to the thing you look for might be
> knowledge bases but I think for a vocabulary you'd wish to
> go for Marc Authority based structures.
> 
> Collections are actually used to sort records in the
> display.

I’m planning to use Collections for media types (books, videos, audio books 
etc.) and provide users with some preconfigured searches (is that the same as 
KBs?).

> Right. But keep an eye on the fields of fft and you might
> also have the case of restrictions to files you can pass on
> in r subfield as firerules.

Thanks again!




Greetlings, Hraban
---
http://www.fiee.net
https://www.cacert.org (I'm an assurer)







Reply via email to