Learn about Edge Delivery Services in upcoming GEM session
SOLVED
Asset versioning - who created latest asset version and when ?
Hi @digarg,
I believe OOTB AEM versioning and timeline functionality is what you are looking for.
Below you can find link to short video that explains, how and when version is created, and what information for each version is exposed to the user.
Here is also sample screenshot the is presenting what you can expect
Hi @digarg,
Sorry I did not catch the information about publish. Anyway below you can find quite detailed description how you can achieve your goal.
Assumptions
- versions are created on author only, so information related to each version is not available on publish. However we have information when and who did last changes against specific asset - this is base for version. This is represented by jcr:lastModified and jcr:lastModifiedBy properties stored under jcr:content node of each asset. In other words you are always publish latest version, so jcr:lastModified and jcr:lastModifiedBy will be relevant for latest version. Even if you revert to older version you will always have data for this specific one.
- after doing any change version is created automatically
- information from jcr:lastModified and jcr:lastModifiedBy are transferred to publish during OOTB publication process - so they are available on publish and can be presented to the page visitor
- solution will use elements/apis provided by ACS - to reduce custom development, and complication in future
- all steps has been described base on demo structure provided by ACS
Solution
I have divided proposed solution into 2 sections, first should allow to achieve main goal, second is optional however will increase end user experience.
Mandatory part
Below steps should be repeated on each asset details page (OOTB there are dedicated pages for images, video, document, presentation - the main difference is set of metadata that could be characteristic for specific asset type) which should contains information about author and date.
- Edit image asset details page - /content/asset-share-commons/en/light/details/image.html
- Add new Metadata component and edit it. Set Label value and Matadata Type
- Add another metadata component and edit it. Set Label value and Matadata Type, Format for Date Configuration
- Open crx/de and navigate to /content/asset-share-commons/en/light/details/image/jcr:content/root/rail/responsivegrid
- Find component added in step 4 (you can recognize it via label value you have set), and add propertyName with value ./jcr:content/jcr:lastModifiedBy. Remember to save changes.
- Find component added in step 4 (you can recognize it via label value you have set), and add propertyName with value ./jcr:content/jcr:lastModified. Remember to save changes.
- Find component added in step 4 (you can recognize it via label value you have set), and add propertyName with value ./jcr:content/jcr:lastModifiedBy. Remember to save changes.
- Go back to /content/asset-share-commons/en/light/details/image.html and publish changes.
- You should see below result on publish server
- Repeat steps 1-5 for all other details pages.
One last comment, why some changes have been done via crx/de. In general not all properties are available from Property Name drop-down. Nevertheless setting it from crx/de will do the job.
Optional
As you can see user name taken from ./jcr:content/jcr:lastModifiedBy is presented as user id. For better experience you can create new Computed property that will be able to display proper first and last name base on user ID - or any other presentation for that will be needed. If you would like to show more details about authors you have to make sure that those data has been published. Custom Computed property requires some development. Here are some links:
jcr:lastModified and jcr:lastModifiedBy won't work and isn't reliable. When someone updates metadata info , both above properties get updated as below and hence this doesn't truly reflects who created version or when was last version created.
