nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Static Document Preview?

ashex

I have a proprietary file format that I'd like to be able to attach a static document preview to. The idea would be to upload it through a data list so you'd be added the file and an image that would be used as the preview.

Is this possible? The idea is that when a user navigates to the file in the document library, the preview would be the image. In the Data List the thumbnail preview would be shown of the image.

Find more posts tagged with

Comments

mrogers

What does the data list do? Another idea would be to add a transformer for your data format. Then share will be able to preview it like any other file.

afaust

Hello,

this should be possible via scripting or a policy. You should only need to set up a rn:rendition child-association from the proprietary file to the static preview document with the child name of "cm:imgpreview" / cm:name = "imgpreview".

Regards
Axel

ashex

Data List would be a way for users to create a catalog of files. The idea is to have a site that users can add this to arranged by industry vertical and other information. Data list would contain all the information for these demos which are the files themselves.

Ideally I'd add a transformer for these files but it requires being processed through another environment, more work then is needed at the moment (it'll eventually get there just not now).

They're using MediaWiki Semantic Forms for the above use case and while it's working, it's cumbersome and we're fairly certain we can achieve the same function through data lists/custom metadata.

ashex

It looks like Renditions will be the way to go. Looking at the details, I'm trying to identify how I'd store the rendition from a datalist form. If I were to store the file inside a zip alongside the image (using a predefined name) would I be able to script extracting the image and adding it as a rendition? Or would that be too intensive?