Context / Motivation
The WebDAV SEARCH API already exposes several properties via PROPFIND, including stable identifiers (oc:fileid, oc:id) and photo-related metadata such as nc:metadata-photos-original_date_time.
However, these fields cannot currently be used consistently in SEARCH queries (SELECT / WHERE / ORDERBY), even though the underlying data already exists and is indexed.
This limitation makes it difficult for clients to implement efficient media queries, cursor-based pagination and incremental synchronization using SEARCH alone. 
This proposal does not introduce new metadata and does not change indexing behavior.
It simply allows existing properties to be used in WebDAV SEARCH:
• oc:fileid
• oc:id
• nc:metadata-photos-original_date_time
These properties can be:
• returned in <d:select>
• used in <d:where> filters
• used in <d:orderby>
Context / Motivation
The WebDAV SEARCH API already exposes several properties via PROPFIND, including stable identifiers (oc:fileid, oc:id) and photo-related metadata such as nc:metadata-photos-original_date_time.
However, these fields cannot currently be used consistently in SEARCH queries (SELECT / WHERE / ORDERBY), even though the underlying data already exists and is indexed.
This limitation makes it difficult for clients to implement efficient media queries, cursor-based pagination and incremental synchronization using SEARCH alone. 
This proposal does not introduce new metadata and does not change indexing behavior.
It simply allows existing properties to be used in WebDAV SEARCH:
• oc:fileid
• oc:id
• nc:metadata-photos-original_date_time
These properties can be:
• returned in <d:select>
• used in <d:where> filters
• used in <d:orderby>