RE: [Bodington-developers] Resource metadata schema

[Peter C. <Pet...@me...>]

> From: Colin Tatham=20
> Looks like the metadata schema that Bodington uses to=20
> describe resources=20
> (Title, Description, etc.) has been replaced by IMS LOM:
>=20
> http://www.imsglobal.org/metadata/index.html

Looks like it.

> I'm wanting to add keywords (and an author) to the metadata, to allow=20
> the search tool to search on keywords, but I can't find the=20
> schema that Bod conforms to...

IMSMD v1.1 I *think*.  I didn't examine this area in detail when
modifying the CP import/export code.

http://www.imsglobal.org/metadata/mdbindv1p1.html

> The proper solution is to upgrade Bod to use a newer schema -- anyone=20
> have views about whether IMS LOM is a good/bad idea?

The entertaining thing here is that the content package import extracts
the metadata from the content package and sets that as the metadata for
the imported resource.  If that's in an odd format, Bod may fail
completely to update its own metadata.  LOM probably counts as an odd
format, at present!

Let's see... <rummage>

BuildingSessionImpl::importMetadata presupposes a top-level metadata
element named "record" in imported metadata, and will fail if that is
not found (BuildingSessionImpl:1450).

BuildingSessionImpl::updateBasicMetadata *also* presupposes a top-level
metadata element named "record" in imported metadata, and will fail if
that is not found (BuildingSessionImpl:1763).  That's called from
createconfirm in Facility, which would seem pretty key to a running
Bodington!

		- Peter