Use case: Data Use Agreement and Collaboration Agreement

loj commented

2025-04-11 08:12:48 +00:00

Owner

Associate signed DUAs and CAs with people and particular resources (data).

loj commented

2025-04-11 08:41:05 +00:00

Author

Owner

Currently Anna Geiger and I try to keep a record of the following information:

Name of data provider/collaboration
Location of associated documents (currently folder on sciebo)
Lead INM-7 Collaborator
Other INM-7 Collaborators
Lead External Collaborator
Other External Collaborators
External Collaborating Institution
INM-7 Coordinator
Status of DUA/CA (pending, active, inactive)
3rd party funding
FZJ D (3rd party funding office) contact
FZJ R (Legal) contact
Link to coordination issue
Start Date
End Date
Notes on process

Currently Anna Geiger and I try to keep a record of the following information: - Name of data provider/collaboration - Location of associated documents (currently folder on sciebo) - Lead INM-7 Collaborator - Other INM-7 Collaborators - Lead External Collaborator - Other External Collaborators - External Collaborating Institution - INM-7 Coordinator - Status of DUA/CA (pending, active, inactive) - 3rd party funding - FZJ D (3rd party funding office) contact - FZJ R (Legal) contact - Link to coordination issue - Start Date - End Date - Notes on process

mih commented

2025-04-14 13:44:59 +00:00

Owner

This is really important!

Few thoughts:

such an agreement should be modeled as https://concepts.datalad.org/s/resources/unreleased/Document/
it should be linked to a physical/digital copy of the document as a https://concepts.datalad.org/s/resources/unreleased/Distribution/

It would be good to understand whether it needs more than what these classes already provide.

Now going through the aspects you listed

Name of data provider/collaboration

Data provider is some kind of Agent (likely an https://concepts.datalad.org/s/social/unreleased/Organization/) -- this instance would have the name attached

Location of associated documents (currently folder on sciebo)

This would be the Distribution of the DUA mentioned above.

Lead INM-7 Collaborator, Other INM-7 Collaborators, Lead External Collaborator, Other External Collaborators, External Collaborating Institution

Are these some kind of signatories with respect to the DUA? If so, they would also be Agents linked to the DUA document via a particular role (something like signatory, or even more detailed)

INM-7 Coordinator

Is this a contact person? Or the legally responsible person at INM7?

Status of DUA/CA (pending, active, inactive)

I believe this might be linking a DUA to a particular project to be executed at INM7, right?

If it is just about the timing, then pending could be whenever it had not yet started, active when it has not yet ended, and inactive after it ended.

3rd party funding

What is being funded here? The data resource, and this is about what funding needs to be acknowledged?

FZJ D (3rd party funding office) contact, FZJ R (Legal) contact, Link to coordination issue, Notes on process

This sounds like we should have a some kind of representation of the process that generates a legally signed DUA, and those would all be properties of that process. Does that make sense?

Start Date, End Date

Of the valid DUA? Or the process that led to it?

This is really important! Few thoughts: - such an agreement should be modeled as https://concepts.datalad.org/s/resources/unreleased/Document/ - it should be linked to a physical/digital copy of the document as a https://concepts.datalad.org/s/resources/unreleased/Distribution/ It would be good to understand whether it needs more than what these classes already provide. Now going through the aspects you listed #### Name of data provider/collaboration Data provider is some kind of Agent (likely an https://concepts.datalad.org/s/social/unreleased/Organization/) -- this instance would have the name attached #### Location of associated documents (currently folder on sciebo) This would be the `Distribution` of the DUA mentioned above. #### Lead INM-7 Collaborator, Other INM-7 Collaborators, Lead External Collaborator, Other External Collaborators, External Collaborating Institution Are these some kind of signatories with respect to the DUA? If so, they would also be `Agent`s linked to the DUA document via a particular role (something like signatory, or even more detailed) #### INM-7 Coordinator Is this a contact person? Or the legally responsible person at INM7? #### Status of DUA/CA (pending, active, inactive) I believe this might be linking a DUA to a particular project to be executed at INM7, right? If it is just about the timing, then pending could be whenever it had not yet `started`, active when it has not yet `ended`, and inactive after it `ended`. #### 3rd party funding What is being funded here? The data resource, and this is about what funding needs to be acknowledged? #### FZJ D (3rd party funding office) contact, FZJ R (Legal) contact, Link to coordination issue, Notes on process This sounds like we should have a some kind of representation of the process that generates a legally signed DUA, and those would all be properties of that process. Does that make sense? #### Start Date, End Date Of the valid DUA? Or the process that led to it?

loj commented

2025-04-15 07:18:32 +00:00

Author

Owner

Lead INM-7 Collaborator, Other INM-7 Collaborators, Lead External Collaborator, Other External Collaborators, External Collaborating Institution

Are these some kind of signatories with respect to the DUA? If so, they would also be Agents linked to the DUA document via a particular role (something like signatory, or even more detailed)

The Lead INM-7 Collaborator is typically the "Lead Recipient" and one of the signatories on the DUA. This is slightly different than "Signing Official", which is someone who has signing authority for FZJ (typically legal or the 3rd party funding office).

In some cases, DUAs require that anyone who will access the data be listed in the agreement. In these cases, I use "Other INM-7 Collaborators" to keep track of these people.

INM-7 Coordinator

Is this a contact person? Or the legally responsible person at INM7?

This is a contact person within INM-7 (typically me or Anna) who is the main coordinator for the DUA/CA process.

Status of DUA/CA (pending, active, inactive)

I believe this might be linking a DUA to a particular project to be executed at INM7, right?
If it is just about the timing, then pending could be whenever it had not yet started, active when it has not yet ended, and inactive after it ended.

This is just about the timing. I agree that this can be described simply using the start/end date.

3rd party funding

What is being funded here? The data resource, and this is about what funding needs to be acknowledged?

This is here because depending on whether or not a DUA/CA is connected with 3rd party funding, it will determine which department at FZJ is responsible. According to Anna:

DTAs without reference to third-party funding are managed by the legal department. However, contracts with a connection to third-party funding (i.e. contracts within the framework of a financially supported project) will continue to be processed by the third-party funding department.

FZJ D (3rd party funding office) contact, FZJ R (Legal) contact, Link to coordination issue, Notes on process

This sounds like we should have a some kind of representation of the process that generates a legally signed DUA, and those would all be properties of that process. Does that make sense?

I think that would make a lot of sense.

Start Date, End Date

Of the valid DUA? Or the process that led to it?

Of the valid DUA.

**Lead INM-7 Collaborator, Other INM-7 Collaborators, Lead External Collaborator, Other External Collaborators, External Collaborating Institution** > Are these some kind of signatories with respect to the DUA? If so, they would also be `Agent`s linked to the DUA document via a particular role (something like signatory, or even more detailed) The Lead INM-7 Collaborator is typically the "Lead Recipient" and one of the signatories on the DUA. This is slightly different than "Signing Official", which is someone who has signing authority for FZJ (typically legal or the 3rd party funding office). In some cases, DUAs require that anyone who will access the data be listed in the agreement. In these cases, I use "Other INM-7 Collaborators" to keep track of these people. **INM-7 Coordinator** > Is this a contact person? Or the legally responsible person at INM7? This is a contact person within INM-7 (typically me or Anna) who is the main coordinator for the DUA/CA process. **Status of DUA/CA (pending, active, inactive)** > I believe this might be linking a DUA to a particular project to be executed at INM7, right? > If it is just about the timing, then pending could be whenever it had not yet started, active when it has not yet ended, and inactive after it ended. This is just about the timing. I agree that this can be described simply using the start/end date. **3rd party funding** > What is being funded here? The data resource, and this is about what funding needs to be acknowledged? This is here because depending on whether or not a DUA/CA is connected with 3rd party funding, it will determine which department at FZJ is responsible. According to Anna: > DTAs without reference to third-party funding are managed by the legal department. However, contracts with a connection to third-party funding (i.e. contracts within the framework of a financially supported project) will continue to be processed by the third-party funding department. **FZJ D (3rd party funding office) contact, FZJ R (Legal) contact, Link to coordination issue, Notes on process** > This sounds like we should have a some kind of representation of the process that generates a legally signed DUA, and those would all be properties of that process. Does that make sense? I think that would make a lot of sense. **Start Date, End Date** > Of the valid DUA? Or the process that led to it? Of the valid DUA.

mih commented

2025-04-25 10:08:03 +00:00

Owner

We now have the concepts of a Dataset and a Project now. I still need to understand how they relate to this.

For a DUA, rather than collection information on a data provider, we might just want to link the dataset the dua is about. Provider info should be a property of that dataset, not a DUA directly.

For collab agreements, my understanding is that they exist within the scope of a defined project. So here also a deduplication of information would be advisable.

@loj do you have thoughts on that?

We now have the concepts of a `Dataset` and a `Project` now. I still need to understand how they relate to this. For a DUA, rather than collection information on a data provider, we might just want to link the dataset the dua is about. Provider info should be a property of that dataset, not a DUA directly. For collab agreements, my understanding is that they exist within the scope of a defined project. So here also a deduplication of information would be advisable. @loj do you have thoughts on that?

loj commented

2025-04-25 10:13:59 +00:00

Author

Owner

For a DUA, rather than collection information on a data provider, we might just want to link the dataset the dua is about. Provider info should be a property of that dataset, not a DUA directly.

I think that makes a lot of sense. This works for me.

For collab agreements, my understanding is that they exist within the scope of a defined project. So here also a deduplication of information would be advisable.

That is my understanding as well. Anna handles most of the collaboration agreements though, so it might be worth double checking with her.

> For a DUA, rather than collection information on a data provider, we might just want to link the dataset the dua is about. Provider info should be a property of that dataset, not a DUA directly. I think that makes a lot of sense. This works for me. > For collab agreements, my understanding is that they exist within the scope of a defined project. So here also a deduplication of information would be advisable. That is my understanding as well. Anna handles most of the collaboration agreements though, so it might be worth double checking with her.

mih commented

2025-05-23 05:25:32 +00:00

Owner

flat-data now has a framework to add the concept of a DUA to.

`flat-data` now has a framework to add the concept of a DUA to.

Rows
Columns

Use case: Data Use Agreement and Collaboration Agreement #7

Name of data provider/collaboration

Location of associated documents (currently folder on sciebo)

Lead INM-7 Collaborator, Other INM-7 Collaborators, Lead External Collaborator, Other External Collaborators, External Collaborating Institution

INM-7 Coordinator

Status of DUA/CA (pending, active, inactive)

3rd party funding

FZJ D (3rd party funding office) contact, FZJ R (Legal) contact, Link to coordination issue, Notes on process

Start Date, End Date