New *RecentChanged similar to *RecentAdded

[Dustcap]

The information from the *RecentAdded list is really convenient for added albums.

Since my tagging of existing albums is in "endless improvement",
I just miss a new similar list which could maybe called *RecentChanged.
This list should only show modified (not added) items.

I did a forum and manual search, but didn't find something referring.

[simoncn]

Based on the experience of implementing Recently Added and Recently Played, it would be a significant amount to work to add a Recently Changed index that works in a similar way.

The simplest way to enable browsing by most recently changed date would be for MinimServer to add a new "special tag" (see this section). The tag name would be Last Modified (#LastModified in indexTags) and its value would be the file system "last modified" date in the format yyyy-mm-dd. The default sort order in the Last Modified index would be most recent first. All files (including added files) would have this tag (if enabled via indexTags), not just a limited number of recently modified files.

I would welcome comments from other users about whether this would be a useful addition to MinimServer and how they would use this tag if it were added.

[Dustcap]

(06-02-2026 16:27)simoncn Wrote:  The simplest way to enable browsing by most recently changed date would be for MinimServer to add a new "special tag" (see this section). The tag name would be Last Modified (#LastModified in indexTags) and its value would be the file system "last modified" date in the format yyyy-mm-dd. The default sort order in the Last Modified index would be most recent first. All files (including added files) would have this tag (if enabled via indexTags), not just a limited number of recently modified files.

That would be a very fine solution for me.

What do you think about the following categories:

LD - modified last day (today and yesterday)
LW - modified last week
LM - modified last month
LQ - modified last quarter year

[simbun]

(06-02-2026 16:27)simoncn Wrote:  I would welcome comments from other users about whether this would be a useful addition to MinimServer and how they would use this tag if it were added.

I don't need a recently modified index, but if there was a way to create a recently added index that covered all albums I'd find that very useful.

Hoping that it's the sliding time window of the current implementation that makes it complex, how about a simple Year > Month > Day hierarchy, something like:

Code:

2026
  >> All
  01
    >> All
    01/01/2026
    02/01/2026
    ...
  02
  ...
2025
...

At each step in the hierarchy you're able to drop into normal browsing mode by choosing the ">> All" selection e.g.

• Select the RecentlyAdded index
• Select 2006
• Select 01
• Select >> All
• Continue browsing [n] albums, [n] items, ... for all albums added in 2026/01
  

I populate a tag called ENCODINGTIME (used by other servers and players to drive recently added) and format it with yearMonth to give me similar functionality, but being able to drill from year to date would be nice (without having to create multiple indexes).

[simoncn]

(10-02-2026 11:17)Dustcap Wrote:  That would be a very fine solution for me.

What do you think about the following categories:

LD - modified last day (today and yesterday)
LW - modified last week
LM - modified last month
LQ - modified last quarter year

The LASTMODIFIED index (if implemented in the future) would not show any categories. It would show index entries in yyyy-mm-dd format like this:

2026-02-11
2026-02-07
2026-01-28
2026-01-15
2025-12-30
... etc.

Clicking on one of these would show all files modified on that date.

As an alternative, it would be possible to use the yearMonth option of the tagOptions property to have the index entries grouped as yyyy-mm, producing an index like this:

2026-02
2026-01
2025-12
... etc.

Clicking on one of these would show all files modified in that month. This is the same as how the Date index works.

There would be no other options for changing this.

[simoncn]

(11-02-2026 12:27)simbun Wrote:  I don't need a recently modified index, but if there was a way to create a recently added index that covered all albums I'd find that very useful.

Hoping that it's the sliding time window of the current implementation that makes it complex, how about a simple Year > Month > Day hierarchy, something like:

Code:

2026
  >> All
  01
    >> All
    01/01/2026
    02/01/2026
    ...
  02
  ...
2025
...

The complexity that requires the number of recently added files to be limited is in how the rescan identifies added files and how the date added is recorded (it isn't the same as the last modified date). I am looking into the possibliity of slightly increasing the limit but there no prospect of extending it to all files in the library.

I think the current way of indexing the limited number of recently added files using finer granularity for the most recently added files and coarser granularity for older additions is the best compromise given that the number of added files is limited. It is important to bear in mind that this feature was designed for recent additions, not as an index for the entire library.

[Dustcap]

@simoncn:
In post #2 you stated not wanting an indexed solution and prefered a "special tag" based solution similar to #AudioQuality.
For me that would be fine and since #AudioQuality has categories, I suggested some for #RecentlyModified.

Since then we're talking about an indexed solution, as far as I understand the posts.

If you'd prefer an indexed solution after all, I would tend to the yearMonth option of the tagOptions property to have the index entries grouped as yyyy-mm.

[simoncn]

Apologies for the confusion. By "special tag" I was referring to what is meant by a special tag in MinimServer as defined in this section. These tags are special because their value is taken from some property of the audio file rather than from a tagged value. They are indexed and browsed in the normal way with no special treatment.

[Dustcap]

For me personally would be a time span of one year absolutely enough.
Everything older could be treated FIFO.

Don't know if this could help or even complicate it.

[simoncn]

With the "special tag" approach, you would get all or nothing.

I am not sure what your setup is. If you can browse your files in Windows Explorer or macOS Finder, viewing the files sorted by modification date (most recent first) is almost equivalent to what you would see by using the "special tag" approach in MinimServer.