Reference document selection: optional view method

[mingard]

For MVP we are using the standard document list view for selecting Referenced documents. This approach covers the requirements for media selection as per Redux.

Post-MVP we may want to consider optional methods for selecting an existing document, similar to previous selection option methods.

Create/Edit should still use the standard document edit view.

@eduardoboucas shared some views on a potential approach https://github.com/dadi/publish/issues/135#issuecomment-291884890

[mingard]

I don't see why we'd want to introduce a select list into the document editor when choosing Referenced documents. It means we have to: a) Define a primary field, which may not always be possible b) Cram in search, filtering and display into a small container

As we discussed @josephdenne, a quick navigation to the appropriate Referenced document collection list view with checkboxes to select documents to Reference is my preferred approach.

[abovedave]

Yep, agreed.

For the post-stuff we should look at how we could handle small 'one-to-many' style datasets (like a tag style situation) because I can see the selectize-style autocomplete pattern being very useful there. Perhaps it's a field-type where you define which API fields your searching against, where to store the text input for a new document etc within the field, rather than giving documents a primary field.

[mingard]

Indeed.

In the tag example we'd need a way to distinguish between a collection that opens full-page and one that can be linked through a basic, or perhaps complex <select> list. It might be a configuration piece, or automated.

[jimlambie]

[input/wireframes from design team required]

[jimlambie]

https://github.com/dadi/publish/issues/135#issuecomment-291899765