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
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
When you go to Duo Search right now, we show the latest listings. This was possible with OB1.0 because each listing had a unique GUID, and kept that GUID across edits.
With the current OB2.0 setup, this is not so easy. As discussed during a technical call with @hoffmabc and @cpacia, my suggestion is to have versioning at the listing level by including a previousEditHash field containing the hash of the previous version of the listing. When a listing is created the first time, previousEditHash would be the empty string and could deemed "new" for display on Duo Search.
Listing versioning is also helpful for ratings, as discussed here.
The text was updated successfully, but these errors were encountered:
When you go to Duo Search right now, we show the latest listings. This was possible with OB1.0 because each listing had a unique GUID, and kept that GUID across edits.
With the current OB2.0 setup, this is not so easy. As discussed during a technical call with @hoffmabc and @cpacia, my suggestion is to have versioning at the listing level by including a
previousEditHash
field containing the hash of the previous version of the listing. When a listing is created the first time,previousEditHash
would be the empty string and could deemed "new" for display on Duo Search.Listing versioning is also helpful for ratings, as discussed here.
The text was updated successfully, but these errors were encountered: