Re: creating a metadata set

Andy wrote:
> Hi Guido,
> 
> Thanks for your reply.  It seems one needs to create a metadata set in xml on 
> the fs and then import it into silva.  Seems to save my MultiListFields just 
> fine.  Seems like using the ZMI to create metadata for silva was never 
> tested.  I guess that's why the link in the service_metadata says 'Browse' 
> and not 'Manage', and also why there is no 'export as xml' feature.  At least 
> the latter would be nice, since one who isn't familiar with the xml format 
> could use the ZMI to create the set, and then export.  Anyways, just a dream 
> I guess ;-)
> 
> Thanks so much for the help!

You can export a set, by appending 'exportXML' to the URL to the set in de 
service_metadata.

Still, creating sets in the ZMI shold still work (although is has some rather 
icky UI aspects, to say the least..). I'll have a look into this. Can you tell 
me what Silva and what SilvaMetadata version you're using?

Further more, some field types have problems when saving metadata, where the 
(multi)checkbox field is most obvious. If an enduser unchecks a checkbox, it is 
not in the POST request. The current metadata system then regards this field as 
not set at all and leaves the current value alone. IOW, a checkbox can be set, 
but not unset anymore...

I did some work recently on SilvaMetadata to overcome some of these 
limitations/problems for a project we're doing. This work has been merged with 
the CVS trunk of SilvaMetadata and Silva last week (just after releasing 
Silva-1.2, so these fixes will be in in an upcomming version).


regards,
jw

-- 
Jan-Wijbrand Kolman
[email protected]