Jump to content

Search the Community

Showing results for tags 'lastplayed'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Third Party Apps
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 1 result

  1. The ASK - It would be outstanding if we could add a LastAccessedDate to the API calls for EMBY. One possible location could be GetItems, FIelds=LastAccessedDate. I do see that there is a Last Played Date that is recorded per an individual playing the content. This should make this a relatively "trivial" addition by defaulting the field to False and writing the Last Played Date to it anytime anyone plays the content. If you want to take it a step further, anytime anyone plays the content continuously for longer than X minutes. The distinction here is a global last accessed date independent of each user's current Last Played Date. The WHY - One of the staples of content management is the ability to determine an item's last access date as it determines the relevance of an item. Most of us do not have unlimited storage, which means if something has never been accessed or played in two years, it is evident that no one cares to have it on there; as such, it should be removed. This could also be helpful data to display internally for those not leveraging API calls. While PLEX did not have this data natively, the ability to pipe Tautulli into the system did allow you to have the data accessible in a programmatic way. The WORKAROUND - The only way I can see to accomplish this today (natively) would be to pull a list of all users. All of their individual last played data, combine, clean up the data, restrict to a date/time window of interest, compare with the entire list, and remove the difference. This, unfortunately, will likely be the path I head down as my need is more immediate. But what could essentially be a single line or two of code to accomplish has now become a multi-series set of loops to build a dataset that can be used for this purpose. I appreciate your consideration, and if I am missing something blatant, please let me know.
×
×
  • Create New...