Hello Vít,

sorry I don't know all the answers.  Probably somebody else will help
you where I cannot.

[...]
>     If those libraries have an oficial identification, you can use the
>     (librarycode)idientifier value in $a, or a simpler $9 librarycode
>     $a number.  Invenio will use those values so that even if you
>     reload your records several times, they will overwrite old
>     records, not creating new ones.
>
>     http://invenio-software.org/repo/invenio/tree/config/invenio.conf#n1573
>
> Thanks! I will test it right away.
>
> I was actually looking at invenio.conf but since I am new to this area
> I didn't connect the dots. What is the difference between external
> number and external OAI_ID? What takes precedence during
> replace/update?

I think that in this case they overlap; Invenio uses OAI_ID (or OAIID)
and external identifier as synonyms; at least, I use 035 for any
external source, either OAI or batch load.  If I'm wrong, please
somebody correct me.

>     > 2. Duplicity checking should take into account library + phys_id
>     > combination. I do not see any other way than to hack bibupload
>     > for this. Am I missing something?
>
>     No need to hack bibload.  You can use the library code as 980 $a
>     (or $b) in case you need to create a collection for each library,
>     but it depends on how you'd like to display those records on your
>     database.
>
> The requirement there is that if there is a another record in the
> database with the same library + phys_id combination then nothing
> happens even when the bibupload is run in replace/update mode. What
> about CFG_BIBUPLOAD_STRONG_TAGS?  What does it mean that they are
> strong enough to resist the replace mode? Does it mean that the
> replace is cancelled or does it mean just that these tags survive and
> other tags from the record are replaced?

Sorry, I have no experience with those STRONG_TAGS, so I cannot answer.

However, my understanding is that if you call bibupload with --insert
(that is, not with --replace) and those records do already exist, they
should be not updated, just skipped.  But again, I haven't tried lately,
you'd better test it yourself.

>     > 3. We would like to move marcXML files to directories OK and
>     > NOT_OK after they are uploaded based on the result of the
>     > upload. Is there a way how a bibtakslet can get this information
>     > or do I need to use callback machine for that?
>
>     If you use 035, the records will be either inserted (new records)
>     or updated (overwritten).  You will get the list in the bibupload
>     log.
>
> Does this mean that the records will be updated based on 035 even when
> the bibupload is not run in replace/update mode? Implementing this
> feature via --calback-url seems to be silly.

As I have wrote you just above, I don't think so, but I'm not so sure...

>     Hope it helps,
>
> Yes, it does. Thank you once more.

Corrections expected and welcome ;-)

Ferran

Reply via email to