You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what problem this solves and why this would be valuable to many users
For some reason I've got some issues in my index and some photos do not have their location extracted or some videos not visible in the Places view despite having the location data. I've uploaded these originals I noticed were missing some data or missing in the search view again and then run reindexing (but without a complete rescan as it takes ages to complete), but it didn't solve it.
Describe the solution you'd like
As indexing issues may occur at any time for many different reasons - I think it would make sense if it was possible to be able to force the indexing process, but only limited to selected files. Even the simplest solution, which would be adding CLI support would be fine for me. Obviously the best solution would be to select the files in the UI and then run some action for them by pushing a button.
Indexing is a super-resource heavy process and takes ages on slower hardware like NAS devices or RPis, thus reducing the indexing time by only executing it for limited dataset would save a lot of time and energy.
Describe alternatives you've considered
Full, forced reindex is not an option as it's taking many days to be run on my NAS. It takes 3 days on my PC when running 24 hours a day. No other way of fixing the index issues that I'm aware of.
Additional context
Screenshot showing a file, that is not shown in the Places view, despite having the location data. The reindex could be an action covered by the contextual button which allows metadata edits etc:
The file has location data, but Photoprism missed it somewhere and it wasn't indexed properly. I did not add this manually:
I expect the solution to cover this case - basically to process te file and extract & process whatever is extracted and processed during the full, forced reindexing process (location, photo name, tagging/labels etc).
PS. I've just noticed the video file does not have the country name despite having the location data - apparently wasn't extracted / processed. I guess something went wrong in the processing chain and the data were extracted, but not processed.
The text was updated successfully, but these errors were encountered:
While you cannot reindex single files, you can search and select folders for indexing as shown in this screenshot taken on demo.photoprism.app:
Unless you happen to have all your files in a single directory (which may also cause filesystem related performance issues), that should provide you with an easy way to only reindex certain files. Please note that a complete rescan is generally not required and only recommended in case of problems or a major update.
Describe what problem this solves and why this would be valuable to many users
For some reason I've got some issues in my index and some photos do not have their location extracted or some videos not visible in the Places view despite having the location data. I've uploaded these originals I noticed were missing some data or missing in the search view again and then run reindexing (but without a complete rescan as it takes ages to complete), but it didn't solve it.
Describe the solution you'd like
As indexing issues may occur at any time for many different reasons - I think it would make sense if it was possible to be able to force the indexing process, but only limited to selected files. Even the simplest solution, which would be adding CLI support would be fine for me. Obviously the best solution would be to select the files in the UI and then run some action for them by pushing a button.
Indexing is a super-resource heavy process and takes ages on slower hardware like NAS devices or RPis, thus reducing the indexing time by only executing it for limited dataset would save a lot of time and energy.
Describe alternatives you've considered
Full, forced reindex is not an option as it's taking many days to be run on my NAS. It takes 3 days on my PC when running 24 hours a day. No other way of fixing the index issues that I'm aware of.
Additional context
Screenshot showing a file, that is not shown in the Places view, despite having the location data. The reindex could be an action covered by the contextual button which allows metadata edits etc:
The file has location data, but Photoprism missed it somewhere and it wasn't indexed properly. I did not add this manually:
I expect the solution to cover this case - basically to process te file and extract & process whatever is extracted and processed during the full, forced reindexing process (location, photo name, tagging/labels etc).
PS. I've just noticed the video file does not have the country name despite having the location data - apparently wasn't extracted / processed. I guess something went wrong in the processing chain and the data were extracted, but not processed.
The text was updated successfully, but these errors were encountered: