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
So changes you make to an asset indexed text aren't visible in the search index until the Work is reindexed, perhaps by saving the work in admin interface. this is a problem when we go adding translation/transcription to existing works, the added text might not end up searchable.
We didn't used to include anything from members in the indexing of the work. So didn't have this issue.
When we crossed that bridge, we forgot it was an issue.
One workaround would just be to reindex everything every night or something, since our indexing currently only takes a couple minutes.
Or we could actually solve it. Perhaps with a new fancy feature in kithe. sciencehistory/kithe#121
(Note, I don't know if this is particularly well-solved in samvera-world either, it would be interesting to check with that community though)
The text was updated successfully, but these errors were encountered:
A simpler way to try to handle this might be just at the controller level for staff UI -- and we have to know that if we are batch-changing transcriptions/translations via some other means, we'll just have to reindex the implicated Works "out of band".
So changes you make to an asset indexed text aren't visible in the search index until the Work is reindexed, perhaps by saving the work in admin interface. this is a problem when we go adding translation/transcription to existing works, the added text might not end up searchable.
We didn't used to include anything from members in the indexing of the work. So didn't have this issue.
When we crossed that bridge, we forgot it was an issue.
One workaround would just be to reindex everything every night or something, since our indexing currently only takes a couple minutes.
Or we could actually solve it. Perhaps with a new fancy feature in kithe. sciencehistory/kithe#121
(Note, I don't know if this is particularly well-solved in samvera-world either, it would be interesting to check with that community though)
The text was updated successfully, but these errors were encountered: