[Feature] Ability to browse/discovery Atlas datasets for usage with Localdocs

[manyoso]

Feature Request

• Allow users ability to create and share localdocs collections by uploading them to Atlas
• Allow users to browser/discovery localdocs collections and use them from Atlas

The UI would have to be worked out, but the basic idea is to allow people to share/modify/update/download localdocs collections with Atlas acting as the hub.

[3Simplex]

The cloud button for each local doc. A blank cloud is not shared, a filled cloud is shared. The lock icon ensures the doc is private and not shared.

A user who has agreed to download or upload shared local docs. Will have the new buttons.

[3Simplex]

In the settings menu. Each collection would be locked by default. After unlocking the collection it could be shared. A collection that is downloaded or shared will be shown as [shared] the button will be unavailable. If it is shared, and, if changes are made to the collection, it will be locked and unshared.

[3Simplex]

The "Shared Docs" are available to find in the download menu in a section for shared docs. Each item will be handled as a standard localdoc unless the option for [auto update] is selected. If [auto update] is not selected, the item will remain locked as it is in use. (ensures no changes can be made) If [auto update] is selected, the localdoc cloud icon will be filled. (maybe with a lightning bolt)

[manyoso]

These are beautiful mock ups and give lots of food for thought! Thanks!

[3Simplex]

These are beautiful mock ups and give lots of food for thought! Thanks!

I was about to make two more, one for the share menu, another for the consent screen. Other than that did I miss anything?

[3Simplex]

After clicking the share button the share menu provides the following functionality.

1. The user will be provided with a contributor template for the upload. (If the collection has already been uploaded, the template will autofill to allow an update.)
2. Clicking the policy button will provide the contribution policy. (You may want an accept button in the policy screen.)
3. The user will sign the upload with the required private nomic API key. (Autofill, The key is provided on the plugin download page.)
4. The user may verify the collection to be uploaded. (Clickable to show contents of collection.)

[3Simplex]

Here is the plugin listing on the download page. (This is where the user will be directed to enable the feature.)

[3Simplex]

Default model selection per collection. Each model will reindex when selection is changed.

[3Simplex]

If only one Embed Model can be used. [Reload/Reindex, Eject collection, Change Model]