Stefan Burkard wrote:
hi slide-users
i'm looking for a repository to store files (in this case PDFs) with additional meta-data.
Perfect, this is what Webdav (and thus slide) is for.
all the meta-data to a PDF-file is stored in a separate xml-document. the PDFs and XMLs will be putted on the server by ftp.
No need for external metafiles : metadatas are intrinsic on the server. No FTP, you can write a very simple java program that browses directories, puts pdf files on the server, reads XML files with metadata and puts metadata on the server. Look at the WEBDAV specifications, and at the slide client library to know the classes you'll need for the importing java program.
so, what is needed to be done in a first step, is to store all PDFs in the repository and associate them with the meta-data in the corresponding XML.
Exactly.
after that the meta-data needs to be searchable and the resulting PDFs in the search-result must be downloadable out of the repository. for performance-reasons it would be great to store meta-data in a database and files in the filesystem.
Metadatas are searchable in a number of ways, including full text searches and stuff. You should look for DASL protocol (which defines searches on webdav servers), the existing DASL implementation in slide and eventually (if you need really custom searches) develope your own extractor. It's possible to specify different storages for files and metadata, so you can sotre files on the filesystem and properties on a database. The database schema is already given from slide, and must be that unless you implement your own store.
additional i need to be able to replace any file and the associated meta-data with a new version, so that the new version is online and the old one could be restored if needed.
Versioning is supported in a variety of ways in slide : auto versioning, check-in check-out, with workspaces .. and a veriety of intermediate steps. See the DELTAV specifications for that.
and finally the meta-data should be extensible, so that new fields can be added without rebuild the entire repository.
Every "field" is a property in webdav language, it's composed by a name, a namespace, and a content, which is usually an XML fragment. So, it does not have a fixed structure, it's always possible to add a new property, delete an existing one etc.
is something like this possible with jakarta slide?
Basically, everything you said.
Hope this helps, ciao, Simone Gianni
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
