Uploading directories

[Michael Ashley]

Greetings - New to SC. We have SC running stand-alone, love the core graphics rendering, all is working fine. I could not find in the documentation how to manage uploading multiple files. Well, what I mean is, in the documentation it says

Remember, in SuperContainer 2, you upload entire directory structures to SuperContainer, so if you have a folder on your desktop named 'CoolStuff' that contains 'MyFavoriteFlower.jpg', 'MyFavoriteTree.jpg', and 'MyFavoriteBug.jpg', you can upload that folder into a single folder in SuperContainer. If your URL is /SuperContainer/Files/19, it will be stored on the server as a single zipped file in 19/CoolStuff.zip.

What we want is to be able to upload a directory of items and have them stored as discreet files, OR most importantly, be able to access them as discreet files, each with their own URL.

What am I missing?

In the above example from the documentation, how would I access MyFavoriteFlower.jpg after uploading CoolStuff to Files/19?

Many thanks,

Michael

[Valentin]

You can upload the files in the directory individually. The example in the docs illustrates that if you upload a folder it will be stored as a zip, upon download SuperContainer applet or plugin will decompress the zip so you have the folder back.

[Jesse Barnum]

To elaborate on Val's point, you would typically have a FileMaker record for each uploaded file. The FileMaker record would have some unique identifier which would be used as part of the SuperContainer URL, and then you can access that file using that URL.

In order to upload these files, your users can do it manually (by creating a new FileMaker record and then dragging the file into the web viewer associated with the URL for that record) or automatically (by using the optional SuperContainer plugin to scan a local directory and call SCSetContainer for each one). If you want to explore the automated approach, you can see an example of that in the demo file that comes with SuperContainer.

[Michael Ashley]

Great, I think I follow. I don't want the user to have to upload individually each file, so I'll check the automagical route. In fact, my goal is to use SC to parse out and manage our massive asset collection, some 40,000 pictures, movies, pdfs. CoreImage is essential for our work, we have a lot of photoshop, illustrator and other files I'd like to be able to render.

I understand in your replies how to do the uploads for individual files. We assign unique ids to everything, no problem there. It's the whole directory uploads that are more of a head scratcher.

It's exactly this functionality that sets SuperContainer into its own class of goodness. Once we have dealt with our own mass of content (all the data is in place and the media are ready to migrate), we want to open up the project to new contributions from team members and the public internationally.

I'll set up the plug-in on our FMSA11 and explore the example file in depth. I figured I'd need to get the plug-in involved in order to really manage the process.

I'll report back once I've done more homework.

Thanks for your prompt, informative reply. We're really looking forward to leveraging SuperContainer (and Scribe) for our solution.

Cheers,

Michael