Updating strategy

[Peter Desmet]

Hi,

I'm preparing a BCI presentation for our collection network here in
Canada (based on Roger's presentation at the TDWG meeting,
thanks :-) ) and I have some questions on the updating strategy of
BCI.

I guess the information propagated through the web services is the
information on the community tab of a collection? And that this
information is initially filled out with information available from
the sources (Index Herbarium, ISCW)? I also guess BCI receives or
reindexes the source information over time?

Now, what happens in the following scenarios?
1. Community info not updated, source info not updated:
community info = source info
2. Community info updated, source info not updated:
community info is used (as always)?
3. Community info not updated, source info updated
source info overwrites community info, which wasn't changed anyway?
4. Community info updated, source info updated
community info gets priority and is not changed?

If these assumptions are correct, its means that once the community
info has changed through the BCI web interface once (and maybe
abandoned later), it cannot get updated anymore via the sources? And
is this true for all the collection info, or just the fields updated
through the web interface?

And multiple sources (IH and Biorepositories for example) probably
adds another level of complexity...

I hope somebody can explain how BCI tackles these problems, because I
expect some questions about this from my audience. :-)

Peter