Sarah,
> A statement of accrual policy (closed, passive, active,
partial/selective),
> accrual method (purchase, deposit)) and accrual periodicity (closed,
irregular, periodic).
>
> This element has always struck me as too packed, i.e. this one element
is supposed
> to cover three slightly different things. I've wondered whether we
need to unpack
> this a bit and actually have three distinct elements (the definitions
probably need some work):
>
> accrualPolicy: A statement of the policy for adding items to the
collection (closed, passive,
> active, selective)
> accrualMethod: A statement of how items are added to the collection
(purchase, gifted,
> deposit, etc)
> accrualPeriodicity: A statement of how often items are added to the
collection (closed,
> irregular, daily, weekly, etc)
This sounds good to me.
> It seems to me that going this route would allow less ambiguous values
for each element -
> which would be a good thing for both humans and potentially machines.
We could even define encoding schemes corresponding to those small
controlled vocabularies, but I'm not sure whether you were going as far
as suggesting that.
> It also seems that accrualMethod (if the definition is tweaked) could
be applied to resources
> other than just collections, though I don't know that it's a much
needed element.
I wasn't sure I understood this bit, but maybe I'm not thinking
laterally enough! ;-) What sort of resource other than a collection did
you have in mind that got items added to it?
Cheers
Pete
|