View for documents with an associated task

I guess, I phrased my goal quite reduced.

Maybe, I give some background. We want to include a larger number of documents into our vault. The metadata card filling needs some handwork and we want to distribute the documents step-by-step via tasks to the colleagues.

The idea is to create a view of the documents having a task. Using the document object gives way more opportunities to refine the results than using the task object, instead.

Please ask, if the explanation is not sufficient. Are there better ways to achieve something like this?

Or, is this not right forum? Do you recommend a different one for placing this question?

Best regards,
Holger

As a general point creating a view that lists all the tasks is easier than creating a view of documents which have tasks (especially where you then want to filter to only certain tasks).  What exactly is the use-case here?  Can you elaborate on exactly what you want to list and what the users are going to do with the data?

This forum is probably the best place, although for more theoretical queries it's sometimes worth speaking directly to your reseller or account manager to run through ideas and potential alternate ways to model the data to achieve what you want to achieve.

As a general point creating a view that lists all the tasks is easier than creating a view of documents which have tasks (especially where you then want to filter to only certain tasks).  What exactly is the use-case here?  Can you elaborate on exactly what you want to list and what the users are going to do with the data?

This forum is probably the best place, although for more theoretical queries it's sometimes worth speaking directly to your reseller or account manager to run through ideas and potential alternate ways to model the data to achieve what you want to achieve.

Thank you for your reply. We setup several document classes (project, library, communication). The thing is that we want to integrated library documents now. My idea was to find all library documents and then filter on various associated task properties. This approach looked promising because the tasks get a "document" property assignment on creation, which might be accessible. (BTW: How can I achieve the same when creating a new object type resp. a new class? A link to a guide would be sufficient.)

Similarly, with your answer, we can find all task and limit the view to associated library documents. This seemed to me equivalent, at first. Thinking about it, it might be sensible to define a "library doc task" and snatching some library document properties for further filtering.

This would give the option of listing:

a) all closed tasks for just the class "library document"

b) all tasks for library documents with property X

Does this explanation make sense? Thank you for your time.

Holger