Combining file upload with creation of DCR

Hi,
We would like to store meta information of PDF files in TeamSite. One way of doing that would be a two step process:
1) Upload the PDF to a directory in TeamSite
2) Create a new data record to capture meta information about the PDF. The data record would include a browser element to tie it to the PDF. Something along the lines of:
<item name="PDF File">
<browser extns=".pdf" initial-dir="/"/>
</item>

Is there a way of combining these two steps into one step? In other words: When the user clicks on the "browse" button he/she should be able to select a file from their local harddrive. When the DCR is saved, then the file should be uploaded to TeamSite and the DCR should be saved.

Thanks.

Ralph

Find more posts tagged with

Comments

Johnny

Two points.

1. Are you aware of TeamSite's ability to store meta data on any file.
This is seperate to DCR's

Read up on TeamSite Metadata in the admin manual.

You basically configure IWHOME/local/config/datacapture.cfg to setup your meta data fields and then use iwmetadata.cgi to fill them in.

Be warned though, some people have mixed feelings about the UI for this system.

2. Search the forums and you will find many discussions regarding uploading of files.

John Cuiuli
Consultant
Sydney, Australia

SBInvoice.dux

Adam Stoller

If you have MetaTagger - you would use a different CGI (it's a LOT nicer than the current OOTB set metadata UI) - and you could even have metadata extracted and applied to the PDF file automatically - read up on MetaTagger for more information - or ask your friendly neighborhood Interwoven Sales Rep to provide a demonstration...

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I agree that the default metadata collection system is garbage, but if you aren't going to be doing automated metatagging you may spend more time getting metatagger configured that just setting up a system that associates a metadata DCR with each binary file. That way you have only one templating interface to learn (and it supports FormAPI, unlike metatagger).

Packed Project.zip

rbuelling

Thanks, guys. I got the information I was looking for. Your help is very much appreciated.

Ralph

Migrateduser

A final thought here... using TeamSite's out-of-box UI may be sufficient for what you're looking for. If you already have MetaTagger, or are looking to get it, you get a more usable, more capable metadata capture UI out of the box... no configuration needed. It's on par with Templating 5.0 so you get inline and CGI callouts, <allowed> tags, plus grouping of metadata elements by tab so they make sense for the end user. Metadata set by TeamSite or through MetaTagger will both be stored as extended attributes in TeamSite.

For the motivated individual, Adobe offers their XMP (eXtensible Metadata Platform) toolkit which allows you to read/write directly from/to PDF documents, PSDs, GIF, JPEG, Illustrator, and other Adobe and extended graphics formats. This is helpful if you need to preserve metadata inside documents when transferring them between different companies/agencies.

Mike