Re: [Exist-development] Metadata in eXist

[Dan M. <dan...@gm...>]

I am not sure I understand so here is an example use case for photography
images.

We could create a trigger under /db/images so that all images that are added
to specific collections that have an image type (.jpg, .png. gif etc.) such
as:

/db/images/foo.jpg

would have an XML fragment automatically created that might contain
information about the image like
this<http://www.exif.org/samples/canon-ixus.html>but in XML format?

Can we control where and/or how we store the metadata?  If we want the
metadata to be backed up it might be in the same collection:

/db/images/foo.jpg.meta

or

/db/images/foo.jpg.meta.xml

or optionally, perhaps it should it be put in a system folder:

/db/system/meta/db/images/foo.jpg.meta

or

/db/meta/db/images/foo.jpg.meta

Does this make sense?

- Dan

On Fri, Jul 30, 2010 at 12:00 PM, Patrick Bosek <pat...@jo...>wrote:

> So, it seems like we're fairly agreed that a new axis is not the way to go.
> I would tend to agree that is the right decision. So the only question left
> is whether to use key/value or xml fragments. I like Wolfgang's method of
> accessing metadata, it seems very consistent and intuitive. Unless I'm
> missing something, I'm still having a hard time seeing value in choosing
> key/value over xml fragment. Since under Wolfgang's suggestion anyone who
> wanted a key/value type metadata set could simply access them as
>
> metadata("/db/doc.xml")/keyOne
> metadata("/db/doc.xml")/keyTwo
>
>
> This may not allow us to store binary data natively in metadata fields. But
> I would contend that in 99% of cases metadata is being used to aid in
> searching for or classifying another resource in the database.
>
>
> As a side note. I'm planning to begin working on implementing this around
> the 2nd week in August.
>
> Cheers,
>
> Patrick
>
>
> On Fri, Jul 30, 2010 at 6:41 AM, Adam Retter <ad...@ex...> wrote:
>
>> > we need to keep in mind that when data is backed up / archived /
>> > extracted outside the system that metadata moves with it.
>>
>> Completely agree with you. But as was mentioned earlier in terms of
>> thinking of ntfs streams, when the backup is done as well as for
>> example doc1.xml being in the backup you could also have doc1.xmd
>> (containing the metadata)
>>
>> > J
>> >
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>>
>>
>> ------------------------------------------------------------------------------
>> The Palm PDK Hot Apps Program offers developers who use the
>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
>> of $1 Million in cash or HP Products. Visit us here for more details:
>> http://p.sf.net/sfu/dev2dev-palm
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>
>
>
> --
> Patrick Bosek
> Jorsek Software
> Cell (585) 820 9634
> Office (585) 239 6060
> Jorsek.com
>
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>


-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1552