The newest version of ADAM (Automatic Digital Assets Manager) lets you group files (often images) into folder (like albums) and also lets you add custom metadata like author, title, description and much more. Adding assets to a content-item just got 10x more powerful.
Content Management Needs Assets
So there are many cases where content-managers need to add a series of files to a single content-item. Common examples are:
- Products with a library of packshots
- Customer showcase with a bunch of screeshots
- Extranet with product catalog and media libraries for images, documents etc.
- Image galleries (with lots of images, possibly structured as folders)
- People profiles with a variable number of additional documents (like CVs, etc.)
- Catalog of real-estate with 1 library of inside-photos, 1 library of photos of the surroundings and another library of documents
There are two basic things that make this difficult. On one hand it's the undefined amount of assets (requiring a 1-item-to-X-assets data-model) and it's the maybe-needs-grouping (where editors expect a folder, not a group-dropdown-field).
The data model for a programmer is fairly straightforward, and all the solutions are setup +/- the same way. BUT it's complicated, and from my experience web-designers find it hard to model this - both from the data side as well as the templating.
...and it needs Metadata
What adds problems is that each asset quickly needs additional information. Often the designer/developer will assume that the file-name will suffice, till an additional requirement appears like: "the real-estate photo should show the author, the gps-coordinates and have a description with keywords for google". So basically each asset needs 1-100 more fields to fill in - and this too causes many issues.
And the metadata should probably be multi-language, and typed, ...
Now Fully Automated in ADAM 1.2
So ADAM 1.2 - part of 2sxc 8.1 - now includes all this. It took us about a week to develop, and now it has
- A new field-type called library - which is a field which allows you to add unlimited files. So a content-item can have one or more of these, allowing you to have a Product content-item with a Photos library and a Manuals library and another Applications library showing customers using the product.
- Each library can also have folders and sub-folders (configurable). This allows you to require that the Applications library is grouped into Albums (folders) while the Manuals are not.
- You can create another content-type - like ManualDescription - which you can then tell ADAM to use as file-metadata. ADAM will then let the editor tag each file with this information.
- You can create even another content-type - like Application Group Metadata - which you can use as folder-metadata. This allows the editor to tag each folder with additional information.
- The Razor Engine has a new API so that you can use AsAdam to access / loop through these assets and the asset metadata.
To demonstrate all this I created a demo-app called Tutorial ADAM. The following screenshots are from that app so and will help you get started.
The Content-Editor Experience
Basically the content-editor needs almost zero training, because as with everything in 2sxc, it's just there, and it just works. This shows a content-entry dialog of a simple record containing an assets field:
As you can see, the screenshots are fairly intutive, and folders / new-folder and files appear directly. Note that most file-types have an own icon (like ZIPs, PDFs, etc.). Upload is drag-and drop.
Metadata is handled with the blue / grey tag. Note that these would not be available if the web-designer didn't configure metadata. As you can see the tooltip would even tell you which content-item describes this asset:
Editing metadata is simply done by clicking on the tag:
So again very trivial and barely needs training. And yes, the metadata supports every possible feature in 2sxc - including WYSIWYG. It could even contain another library of assets.
The Data-Modeling Experience
Adding such a library field is also very, very easy. Basically you'll add a File / Hyperlink field and choose the type Library - like this:
To configure Metadata - if you even need it - first create the content-types (in this example they are called Group Details and Screenshot Details:
Then you'll have to tell the Screenshots-field to use these metadata-types. This is done in the field-configuration of Screenshots:
Again - straight forward, easy to do. After this the content-editor already has the UX described above.
The Coder / API User Experience
We're really keen on providing solutions, not just tools. Because of this we spent many hours figuring out how the code should be and trying various API. The following example shows a C# loop showing the screenshots:
As you can see line 9 contains the foreach-loop and line 11 creates the thumbnail with a title showing the name. Line 14 shows you the WYSIWYG-description retrieved from the Metadata.
The API is very smart, so that it won't cause errors if the metadate is missing :)
And one more thing: the new code-editor (in 2sxc 8.1) automatically gives you ADAM snippets for all library-fields. This should really make it easy to get things going:
Export / Import Works Too
Another days work was invested to ensure export/import works, because many things like folders can have metadata, but were never included in the export. This too was ensured.
Note that an App containing ADAM will now include all ADAM assets - and because of that it can easily be 10mb or even 50mb. Be aware of this when you re-import it somewhere, because you often have web.config settings limiting the upload size.
Try it yourself!
You will need the newest 2sxc (at least 8.01.00) and the demo app.
Love from Switzerland,