I don't know how to browse through categories in CIFS. Any help?
CIFS We will continue to evolve the CIFS interface to simplify access to the repository and ultimately replace shared drives in the enterprise. In addition to continually improving performance and scalability, the 1.4 release will expose more of the repository functionality through the explorer interface. A virtual file interface will be exposed by making categories in the system appear to be folders in the file system, thus allowing users to browse (read-only) through categories through the explorer interface. Files can also appear to exist in multiple categories. In addition, virtual executables will allow us to expose actions that would not normally be available in the explorer interface. By creating a simulated executable, we can provide actions such as check-in/check-out and force capture of metadata. In addition, we can expose links to other files and web interfaces using simulated files.
I don't believe it's possible yet - it's something we'd like to add though.
Kevin
This is something I spoke with Dave C. about back in July. It seems like it would be really nice to be able to project different M2 objects as folders in the various file system adaptors/views.
One idea I had was a browse able aspect. I can't remember all the issues we came up with but there are some semantic issues that get you in to trouble. Basically Browse able would have to mean something like: project me as a folder but it doesn't really mean you act like a folder in other ways.
Once you get in to acting like a folder where you can add contents, remove contents, update contents, update metadata of contents you are in a whole new world.
If you provided the right hooks in the base aspect you could get some really neat behavior. "When you add a document to this item that is projected as a folder it does X with the item" where the behavior is overloadable for the type, some would simply add properties (like a tag which would just add a child tag),others would create similar associations to traditional folders, while still others could do other interesting things with the inbound and outbound content.
Think about most of your content. An image is a single document….. Or wait…. is it? What do you do when you have renditions? So you have an image - you might have a High Res, a web res, n number of thumbs, a black and white etc….
What about video… surely that is a single document… or wait is it? You probably have the video itself with 4 different encodings and a still to show before the video loads…
It turns out that using a folder to represent the asset is pretty cool because you can add the actual components under the folder that make up the asset (I would say renditions but that is not broad enough and clashes with other terminology)
One really cool feature is that as a folder your image becomes brows able. The problem of course is that an image is not a folder – so the model is a bit awkward.
You can apply this idea to all kinds of objects in the repository: assets like images, videos, audio, stories that have xml and other types of assets, categories etc…
