On Dec 11, 2011, at 11:00 PM, Karen Coyle wrote:
I'll let you battle that one out with Simon :-), but I am often at a loss for
a better term to describe the unit of metadata that libraries may create in
the future to describe their resources. Suggestions highly welcome.
I'm sure you're
like to
experiment with it for some ongoing work that involves ingesting archival
collections into Fedora, and then editing them with Hydra and viewing them
via Blacklight.
- Tom
On Aug 8, 2010, at 8:13 AM, [Your Name] wrote:
I'd like to share an alternative approach that we're
I'd like to share an alternative approach that we're pursuing here at UVa. It
doesn't speak quite directly to operations on finding aids by themselves, with
no attention to representing on-line the collection so described, but more to
those situations where you make an attempt at a full digital
Mike Taylor writes:
Fedora,
The problem there, as I understand it is that Fedora expects
everything to be in one directory. This setup in inimical to the
Debian setup.
Personally, I would think that Fedora is well beyond anything you're describing
as desired, but just as a point of
How about feeding back from web request stats?
Things that get pulled more often are probably more popular.
It's admittedly not very clever, but it would be easy to implement...
---
A. Soroka
Digital Research and Scholarship R D
the University of Virginia Library
On Dec 7, 2009, at 5:56
There's been some interest lately on this list in the use of W3C XForms for
library metadata (e.g. MODS, EAD, VRA Core...). Several institutions have
committed in one degree or another to their use, and many more are
investigating the possibility. To provide a venue for more specific discussion
In discussion with colleagues around this topic, the question of
controlled vocabularies has been prominent. We're looking to move away
from list instances that are packed into the XForm at render time to
lists that are exposed from other services through REST interfaces,
which can be
