About .ion/metadata/db we can see the for 3.0 but I more and more agree with you about the need of dropping file storage for db storage. An other example in that direction is files inner metadata (ID3, EXIF, etc.). With the "all in file" way of filebrowser, those features are just too slow to be usable (open the file, seek for metadata, etc.). An other example is file order, that would be stupid (I think ;-) to store in an .ion file.
I have already written and changed your both functions for my personal purpose:
_filebrowser_save_description_file($data)
was pretty simple to modify and input $datas into the db Drupal.
_filebrowser_load_description_file($path, $replace = NULL)
is a bit harder because we don't need the path but the $fid instead.
I will post a dev when i will have the time to test it completely.
But know, we should find a clever way to do the job. The one I was thinking about is an "import metadata" action that can be triggered with an action or can be configured in the node to be done every XXX seconds (0=> each time a dir listing is viewed).
By "Import metadata" you mean the action to read the metadata ID3, EXIF, XMP, etc of a file ?
I work for a company that manipulates +/- 5000 images every two month (Magazines), and there is a huge quantity of informations that might be imported in this case. Shall we have a limitation ?
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | filebrowser_metacontent.tar_.gz | 1.35 KB | Nicolas Georget |
Comments
Comment #1
Nicolas Georget commentedYoran,
Here's a first version to implement the metadata into the db. Therefore i added a .install (_update_6215) to alter the table
node_dir_listing_contentwith a new field calledmetacontent.I called the module filebrowser_metacontent because it might be confusing with your Metadata (created, modified, mime-type, etc...). Especially if you expect to add/edit inner metadata like ID3, or IPTC.
I think i have an issue when you edit the node and display the MetaContent field in the Folder Presentation:
1) The "Description" column appears always
2) you have to force the refresh of the node to display the Metacontent column.
Do not know why :(
Comment #2
Nicolas Georget commented1) The "Description" column appears alwaysMy Bad, i never noticed that if there's any
descript.ioninside the directory, the column is still displayed.Comment #3
Yoran commentedFirst thank's for your work. The only thing I'm not sure about is adding a column to node_dir_listing_content. I'd rather preferred a dedicated table.
But anyway, this is actually this give me 2 ideas :
1/ we can make a "modules" subfolder to filebrowser in order to store such contrib (ready to play with git ? ;-). This can be also the place for features like "unzip" or my two privates modules managing images and videos.
2/ we can also unbloat filebrowser this way by putting my core implementation of metadata hooking dedicated to .ion files.
Comment #4
Nicolas Georget commentedTotally agree! As my previous comment, EXIF metadatas can be huge.
Anyway, we have to find a best way to display all of the informations. The field "MetaContent" as i did is not enough.
I do that on my development environment. No problem for git. I use git for my own purpose (XCode and TextMate) but never use git for Drupal. Is it really painful ?
Unzip feature is actually useful. You remember also the possibility to zip a folder also, and not files only.
The audio might be possible: #723624: Inline Audio Helper. I have my own one too that track (record into a table) all the download actions: What file, by who, when, md5 hash, etc...
What did you implement for images and videos ?
Sure. But in the case of you don't want to use .ion files anymore (deprecated) we should have a batch that import .ion datas into the db.
Comment #5
Yoran commentedActually GIT integration with drupal is just perfect. I was surprised how simple it was to use it.
About image/video, I made a complete photo/video gallery system using filebrowser & icon view... Those two modules mainly implements thumbnail hooks.
For zip/unzip, we can move all stuff in a filebrowser_archive module, an yes, implements zipping folder. IMHO, we should drop PHP/Zip support to use server binaries (tar/bzip/zip/gzip/rar/etc...)
For .ion, I'm not quite decided if you should carry on writing on it. If we decide not to, we can see .ion files as a metadata source, same as exif, ID3, etc...
Anyway, if there is no new bug in 2.x, I think this should be placed in a new 3.x version as we'll have to work on database and, why not, make D7 compatibility also.
Comment #6
Nicolas Georget commentedYou mean the possibility to read/write metacontent in any multimedia files ?
I just ask because i had to do that for a big french press company (starting with the editors/photographers to the printer and colorimetric stuffs) and it was neither more nor less than a Adobe Bridge :( it was a nightmare and many sleepless nights...
i.e. #707792: ZIP archive UTF-8 filenames problem
But seems to be easy. I will try on Monday ;-)
You underestimate me ;-)
Seriously it will depend of the goal. If it's just to add a description field, that's fine. If it's for read/edit other existing metadatas, it's an another story. I will send to you a email; just to clarify the goals.
Comment #7
clivesj commented