<div class="gmail_quote">On Mon, Mar 30, 2009 at 9:06 PM, Nicu Buculei <<a href="mailto:nicu_gfx@nicubunu.ro">nicu_gfx@nicubunu.ro</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">Jochen Staerk wrote: >> (I'm wanting to know if I should continue putting clipart in or wait until >> 0.19. I dont really want to add them again.) > > What do you mean by you don't want to add them again? Once you added > them of course they will stay but the snapshot of 0.19 has already been > taken so if you upload pictures now they will be added to the release > after 0.19. </div>On top of that, I hope we will restart releasing often and the next release (0.20) is not far away. So don't wait, upload as soon as you have images ready, they will be available in the website and the daily tarballs, up for the end-users to grab and hopefully not after a long time in the next packaged release.</blockquote><div> I'm not sure I follow, but I'll smile and nod. Or rather I'll let my curious-techno side get the better of me and ask lots of "dumb" questions. :-D To clarify my question, what happens when I upload a single image? It goes to a storage place on the website, and any information about it goes to a database? 0.19 is a cosmetic/frontend change that doesn't modify the database or the image storage place? I don't know how the snapshots work either. What's the purpose of them? What's a tarball? What am I supposed to do with them? How do I access them from the site? What I meant as in "not wanting to add them again" was, it takes awhile to upload with all details, one by one if you have more than 10 clipart. Especially if you go to the trouble of making them specific for OCAL. I've already gotten rid of my source images (I have limited storage space on my local computer). Which means OCAL has the only copies of what I've uploaded. It would be troublesome for me to upload those cliparts again. Does that better explain "I dont want to upload them again"? </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"> >> Does OCAL have a mass upload facility? PHP is able to mass upload (also the >> site admins can do ftp batches), but what facility is there for registered >> joe blogs? > > no idea. AFAIK OCAL does not have a mass upload because ccHost has none. </div>We used to have such a feature in the old website and is missed: basically you had to fill somehow the metadata in the SVG files (either with Inkscape's dialog or from command line in batch mode), make a archive (zip, tarball) and upload that. I think the lack of this feature is what had kept us away from importing all the images from the old site (at least it delayed *my* effort in doing so for over a year). </blockquote></div> I think not having a mass uploader for registers users is a problem for OCAL, and a stumbling block for OCAL's growth. Also, since ccHost can't read MetaData (yet!) is there a manual solution that we could fall back on/develop? From what I can see after reseraching a little, there are a few routes we could take in the multi-upload idea. The main thing is being safe with file uploads. #1. User uploads a zip file. OCAL dumps it in a temporary folder. OCAL opens the zip. Scans for images with .svg file extension. OCAL deletes anything that is not a .svg (including any other image files.) I.e. multiple uploads only allows .svg files. Background scripts that are coming (yes?) can make the .png thumbnails for them anyway so all we need are the svg files. #2. Making a special Multiple File Upload page similar to <a href="http://openclipart.org/media/submit/clipart">http://openclipart.org/media/submit/clipart</a>. Multiple upload boxes, and next to each one, an input field for the tags? My reasoning with this is that anyone who batch uploads will *probably* already know what they are doing. Let's simplify so that we can fit more uploads on. I see the ability and space already available on OCAL as allowing upwards of 10 files. (as seen in this quick mockup <a href="http://img219.imageshack.us/img219/1839/concept.jpg">http://img219.imageshack.us/img219/1839/concept.jpg</a>). All that needs doing (to my limited understanding of how ccHost works with php... is working with the multiple php upload scripts. Of course you also need file checks, safety features as well, but if you're multiple uploading manually you dont need the "featured artist", "suggested tags", "popular tags", "NSFW", "or the "publish now" button. These informations can be edited after the upload in the individual files pages. The uploader can then edit things manually or wait until the file has been checked by an admin (as all new uploads get the unchecked tag anyway.) I know ideally automatic reading of MetaData is desired, but since ccHost doesnt have that ability (yet!), my opinion would be that we should have a manual way as well. Double redundancy - I like. Also a bonus of that is that manually trying something might make it easier to make an autoscript later on. Rearranging the lego blocks so to speak. Are any of these following scripts hackable/useful with info? I don't know which ones would be suitable for an Open project so please be careful and research any of these links carefully. These are for ideas only. Perhaps they can spark something that we can use on OCAL. Or even use. Multiple Upload scripts: <a href="http://www.phpeasystep.com/workshopview.php?id=2">http://www.phpeasystep.com/workshopview.php?id=2</a> <a href="http://www.webmasterworld.com/php/3361474.htm">http://www.webmasterworld.com/php/3361474.htm</a> <a href="http://www.usenet-forums.com/php-general/52153-php-batch-uploading-multiple-files.html">http://www.usenet-forums.com/php-general/52153-php-batch-uploading-multiple-files.html</a> <a href="http://www.daniweb.com/forums/thread141715.html">http://www.daniweb.com/forums/thread141715.html</a> <a href="http://www.phpclasses.org/browse/package/3772.html">http://www.phpclasses.org/browse/package/3772.html</a> <a href="http://www.phpclasses.org/browse/package/338.html">http://www.phpclasses.org/browse/package/338.html</a> Things to have a look at: <a href="http://freshmeat.net/projects/uupload">http://freshmeat.net/projects/uupload</a> <a href="http://freshmeat.net/projects/httpfileuploadapplet">http://freshmeat.net/projects/httpfileuploadapplet</a> <a href="http://freshmeat.net/projects/easy_upload">http://freshmeat.net/projects/easy_upload</a> <a href="http://freshmeat.net/projects/phpforms">http://freshmeat.net/projects/phpforms</a> <a href="http://freshmeat.net/projects/phpwebfilemgr">http://freshmeat.net/projects/phpwebfilemgr</a> -- Cheers Chovynz