[Silva-general] bug?: metadata in full media import

[Marc Petitmermet]

On 09. Mrz 2007, at 13:14 Uhr, eric casteleijn wrote:

> Marc Petitmermet wrote:
>> silva-1.5.10
>> i wonder if this is really the intended behavior. we have the  
>> following setup:
>> container        metadata
>> /                defined here !! <----
>> /foo/            acquired from above
>> /foo/bar/        acquired from above
>> /foo/bar/a/      acquired from above
>> /foo/bar/b/      acquired from above
>> /foo/bar/b/      acquired from above
>> now i make a full media export of /foo and import it somewhere  
>> else. the setup is now as following:
>> container                       metadata
>> /somewhere/else/foo/            defined here <---- same values as  
>> in / at original location
>> /somewhere/else/foo/bar/        defined here <---- ditto
>> /somewhere/else/foo/bar/a/      defined here <---- ditto
>> /somewhere/else/foo/bar/b/      defined here <---- ditto
>> /somewhere/else/foo/bar/b/      defined here <---- ditto
>> shouldn't it be "acquired from above" here for every imported folder?
>
> Currently, on export, all the metadata gets explicitly written out  
> into the xml, so any acquired metadata in the original is indeed  
> explicitly there in the copy. We probably have to build an option  
> to switch this off

will this be an-all-or-nothing option or a tun on/off transformation  
of acquired to explizit option? as you know we have many layout  
configuration options in the metadata and having all of a sudden not  
acquired but explizit data leeds to unexpected behavior and unwanted  
layouts (it took me some time to figure this out). apart from that it  
takes a considerable time to manually clean up the metadata  
information. this is important when people want to fill in content  
offline using a silva instance running on their laptop and then  
making a full media export and then import on the server.

regards,
marc