Storing JPG, BMP etc

, ,
1

Hi,

I was tring to test uploading the BMP files with the following xml schema generated.

<?xml version="1.0"?>
<ino:collection ino:name=“MyImages” ino:key=“ID001”>

<ino:doctype ino:name=“Image” ino:key=“Image2” ino:options=“READ INSERT UPDATE DELETE” ino:structure-index=“CONDENSED”>
<ino:node ino:name=“Image” ino:key=“Image3” ino:obj-type=“ANY” ino:parent=“Image2” ino:search-type=“no” ino:map-type=“NonXML”/>
</ino:doctype>

</ino:collection>

I then Used the TII to and browsed the file hi.bmp and pressed upload.

<?xml version="1.0" encoding="iso-8859-1" ?>
- <ino:response xmlns:ino=“http://namespaces.softwareag.com/tamino/response2” xmlns:xql=“XQL FAQ (XML Query Language - Frequently Asked Questions)”>
- <ino:message ino:returnvalue=“0”>
ino:messagelinedocument processing started</ino:messageline>
</ino:message>
<ino:object ino:collection=“ino:etc” ino:doctype=“ino:nonXML” ino:id=“4” />
+ <ino:message ino:returnvalue=“0”>
ino:messagelinedocument processing ended</ino:messageline>
</ino:message>
</ino:response>

When I query,
http://localhost/tamino/MyStore/MyImages/Image?_xql=*
.I find following while querying through my Browser

ino:messagelineXQL Request processed, no object returned</ino:messageline>

Regards
Pushparajan

2

The clue is the response to the upload in the element
<ino:object ino:collection=“ino:etc” ino:doctype=“ino:nonXML” ino:id=“4” />


Your bmp was loaded to collection ino:etc
doctype ino:nonxml. This is the default container

To upload correctly you must set
the url in the TII to
http://localhost/tamino/MyStore/MyImages/Image

If you want to give it a name like holidaySnaps1.bmp then set the url to

http://localhost/tamino/MyStore/MyImages/Image/holidaySnaps1.bmp

This provides enough information to determine where the

3

:slight_smile: Thanks.

Can I andd additional(Custom) attributes like

versionstatus=“Published” date=“12/12/2001” obselete date=“1/1/2002”

to the image I’ve uploaded. How do I do that.

Regards
Pushparajan

4

Hi,

additional attributes will not fit with this apporach. Your request takes you right in the realm of metadata. Yet, there’s an effort for associating any metadata with documents, it’s called WebDAV and Software AG - by coincidence - just released the Tamino WebDAV server. Here, every document (be it XML, JPG, BMP, …) has an metdata document associated that is perfectly extensible by every attribute you see fit. So, I recommend you delve in the details of this by looking at WebDAV.org and give the Tamino WebDAV server a try Tamino WebDAV Server (it’s a free of charge add-on to your Tamino server).

Best regards, Andreas

5

If you can’t use WebDav The other way to associate properties to documents is to create a meta data doctype and for every instance of the dcoument you want to describe another document which contains the descriptive data and points to the described document via a URL. Then you can do queries on the meta data and retreive the URL of the graphic in Tamino.

If you don’t want to reinvent the wheel completely that I suggest to use RDF format which is designed for precisely this scenario.
http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/

<?xml version="1.0"?>
<<Description
xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"about="http://localhost/tamino/MyStore/MyImages/Image/holidaySnaps1.bmp ">
<s:versionstatus>Published</<s:versionstatus>
<s:publishDate>12/12/2001</s:publishDate> <s:obseleteDate>1/1/2002</s:obseleteDate>

6

If you can’t use WebDav the other way to associate properties to documents is to create a meta data doctype and for every instance of the dcoument you want to describe, create another document which contains the descriptive data and points to the described document via a URL. Then you can do queries on the meta data and retreive the URL of the graphic in Tamino.

If you don’t want to reinvent the wheel completely that I suggest to use RDF which is designed for precisely this scenario.
http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/

<?xml version="1.0"?>
<<Description
xmlns=“http://www.w3.org/1999/02/22-rdf-syntax-ns#” xmlns:s="http://mycompany/ourns/docs"<BR>about="http://localhost/tamino/MyStore/MyImages/Image/holidaySnaps1.bmp ">
<s:versionstatus>Published</<s:versionstatus>
<s:publishDate>12/12/2001</s:publishDate> <s:obseleteDate>1/1/2002</s:obseleteDate>

If you can find a public descriptive vocabulary for your data like Dublin Core http://purl.oclc.org/metadata/dublin_core/ has for documents
and use that instaed of making up your own - you have the prospect of exchanging metadata with other companies in your industry some time in the future.

The use of RDF syntax and RDF Schemas may also permit you to use and reuse RDF based tools.

In my group we have an RDF Schema driven query tool which finds HTML documents in Tamino etc by their meta data.

[This message was edited by Nigel Hutchison on 11 Oct 2001 at 11:11.]

7

Hi,

should I maintain a seperation collection for the metadata. Other wise it seems to upload to the ino:etc collection. In that case how do I create a schema for rdf.

<?xml version="1.0" ?>

DC:Title The Future of Metadata </DC:Title>
DC:Creator Pushparajan </DC:Creator>
DC:Date 2001-01-01 </DC:Date>
DC:Subject Metadata, RDF, Dublin Core </DC:Subject>

Regards
Pushparajan