"Last updated on" on Search Results page

Completed

9 Comments

  • Scott
    Comment actions Permalink

    Hello Ryan,

    Slightly confused. You say "We have an attribute on article and community post objects for "updated_at". However, we have chosen not to expose it.". The updated_at is clearly exposed for the article object. I am using it now in our site.

    If "updated_at" is good enough to be used as part of the article object, why is it not good enough for the search results? I understand that moving an article or doing something as simple as correctly a grammar error causes the updated_at date to be set to current date/time, but I would rather have that then showing a date that then created date which may be many years in the past. The udpated_at would fit my use case.

    1
  • Ryan McGrew
    Comment actions Permalink

    Hey Scott,

    You are correct that the updated_at property is not currently in the search result object. I have a ticket in our backlog to investigate this as the decision was made a while ago. I'm unsure at this time if it was just an oversight or if there's a technical issue for not providing it.

    Thanks!

    0
  • Ryan McGrew
    Comment actions Permalink

    Following up on this.

    We have an attribute on article and community post objects for "updated_at". However, we have chosen not to expose it. This is due to the fact that updated_at is not a representation of when an article or community post was last edited. It is an indication of the last time the record was touched which can happen in a number of different situations that you may not expect. When things like tags, sections or categories are updated. We have seen this cause unexpected updated_at dates in the past which isn't a great experience so we've decided not to provide it via Curlybars.

    We are working on more robust revisions for Articles, as you can see in Yesterday's release of the History View for articles in Help Center. We are hoping as we roll out new features for this that we can provide some utility around providing something that will fit your use case.

    Thanks!

    0
  • Kristof Litavecz
    Comment actions Permalink

    Hi Ryan,

     

    I agree with Scott. I understand why created_at would be the default, but there are indeed use cases when you would want updated_at to be displayed in the search results. Depends how you manage your help centre, I guess. So if the option was available, I am sure that admins who go this deep in the templates design would know what they are doing. 

    0
  • Phil Morgan
    Comment actions Permalink

    Hi Ryan,

    We would also like to display updated_at in search results, notwithstanding the current limitations of this attribute.

    We often update articles with new information. It looks very poor when our customers perform a search and see results dated 2 years ago, when we have actually updated the article in the past 24 hours.

    This is important enough to our customer service team that we will have to migrate away from ZenDesk if this option is not made available to us.

    Cheers,
    Phil

    0
  • Ryan McGrew
    Comment actions Permalink

    Hi Phil,

    I appreciate your concern and as I was hoping to make clear in my earlier post, it's something we're looking into supporting longer term. However, given that the current implementation of updated_at is insufficient for use in this way. Once we have a better way to expose the information you're looking for, we will update the search results object with that attribute.

    In the meantime, if it's something that's very important and that you'd like to work around, you could request this attribute from the Article API for the articles displayed on the page. Not an ideal solution, but something that could work.

    Thanks!

    0
  • Phil Morgan
    Comment actions Permalink

    Hi Ryan,

    Thanks for your reply, the current implementation of updated_at would be sufficient for our use until there is a better way :)

    Can you link to any inormation on 'how to request this attribute from the Article API for the articles displayed on the page'?

    Thanks,
    Phil

    0
  • Ryan McGrew
    Comment actions Permalink

    Hi Phil,

    Apologies for the delay in response. You'd need to make an AJAX request to the article show API (documentation here) to retrieve the updated_at attribute from the object that is returned. You could inject that information in the DOM to show to users for each search results. As I said, not idea but a possible work around.

    Thanks!

    0
  • Ryan McGrew
    Comment actions Permalink

    Hey All,

    We've recently added an edited_at property to articles in the search results object as well as the article object so this should now be available for use.

    Thanks!

     

    0

Post is closed for comments.

Powered by Zendesk