On Nov 28, 2007 4:37 PM, Larry Stone [EMAIL PROTECTED] wrote:
I agree that adding techMD to the METS is architecturally the right
thing, but there is already a better (or at least, adequate..) technical
metadata standard format in PREMIS. There is already a PREMIS crosswalk
for the
I agree that adding techMD to the METS is architecturally the right
thing, but there is already a better (or at least, adequate..) technical
metadata standard format in PREMIS. There is already a PREMIS crosswalk
for the import/export METS packager which you can cannibalize, see
Okay, I did a little bit of scouting around today, and I discovered
that this gets really hairy really fast, but we probably can do
something about it, if we're willing to create a DSpace-specific
metadata schema just to hold bitstream information (which might not be
the world's worst idea,
I haven't looked at the Manakin code, but the MIME media-type of a Bitstream
must be coming from its associated BitstreamFormat -- so why not get
the human-readable name from the BitstreamFormat as well? There is no
need to establish a separate map of MIME-type to user-friendly name
when it
(Subject changed to keep from hijacking the earlier thread.)
For instance, the hierarchical structure of the collections could be
modelled in a simple XML or HTML document, and this hiearchy file could
be read by Manakin and used to add contextual information and links to
the web pages it
On Wed, 2007-11-21 at 16:43 -0600, Dorothea Salo wrote:
(Subject changed to keep from hijacking the earlier thread.)
For instance, the hierarchical structure of the collections could be
modelled in a simple XML or HTML document, and this hiearchy file could
be read by Manakin and used to
6 matches
Mail list logo
