Update page modified/updated by Trigger after publishing files for Stored Search

(Anewport) #1

We have several Stored Search pages which show content that is updated daily. The problem we are facing is that the pages with the search nested within them do not show the most recent date that a file was added, resulting in our footer 'last updated' text seeming quite outdated.

 

From what I can tell so far there is no option to set up a Trigger to fit our issue. What I am trying to achieve is:

  • User uploads file to a specific location and publishes
  • Search Page with Stored Search shows new content throughout these pages
  • The page that has Stored Search results nested needs to be updated to print the correct modified/updated date

There doesn't seem to be a Trigger that says "when file is created here, update assets X, Y, Z". I'm not particularly fussed with what field of the page is updated, as long as the result means printing a new date on the front end for our users.

 

Hope I'm being clear here but if not I'll try to explain better. Any thoughts on how to solve this one?

(Nic Hubbard) #2

Couldn't you just nest another Search Page in the footer that lists the updated date of the most recent uploaded file? Then it would always be up to date.

(Bart Banda) #3

Couldn't you just nest another Search Page in the footer that lists the updated date of the most recent uploaded file? Then it would always be up to date.

 

Yea, and you just have to set it to list 1 asset, as you just need the first asset's date value. 

(Anewport) #4

I think you might have a good solution but I'm going to have to create a lot of Search Pages or Asset Listings to solve it that way. Our 'last updated' text appears in the site footer so it is generated via design tags and due to placement it can't be included as a nested content section within a Standard Page; the site in question is www.jobs.act.gov.au

This might be easier to explain once you can visualise the architecture in the back end which was developed to cater for different needs of front end grouping and administrative staff functions (i.e. uploading).

 

Just realising now that the updated date I'm after would generally be based on a Standard Page, instead of files but that is minor.

 

The files themselves sit underneath a Standard Page which sits under a Folder, that is under another Folder. E.g:

ACT Auditor General's Office [folder] > Permanent [folder] > Position [standard page] > Associated files

[attachment=693:jobs-folder.jpg]

We then need these job positions displayed by category which is chosen via metadata and a Stored Search page nested across several Standard Pages.

[attachment=695:search-by-category.jpg]

Additionally the should be displayed via agency.

[attachment=694:search-by-agency.jpg]

Lastly there are the other pages that lists all jobs vacancies, all by permanent or temporary status, and the home page showing most recently added.

[attachment=692:all-vacancies.jpg]

 

So if I was to use a Search Page or Asset Listing per page, I think I would need to create one per page as indicated above in the screen shots, which is a lot. Nesting via a design area wouldn't allow me to pass a dynamic parameter per page to choose the correct folder from which to obtain the most recent date.

  all-vacancies.jpg (4.75 KB) jobs-folder.jpg (34.4 KB) search-by-agency.jpg (37 KB) search-by-category.jpg (23.3 KB)