[Allpartners.music360-beta] Visit Gema to Amsterdam

Denis Guilhot dguilhot at bmat.com
Thu Feb 15 14:49:00 CET 2024


Hi Jaap,

Yes, definitely. We will have to update the Consortium Agreement and submit
an amendment to the PO.
But these modifications will have to be specific to what task is agreed
upon from both sides, what access rights are granted... Also, I think the
PO will ask the reasons, objectives, and details of the collaboration
before accepting their inclusion in the project. So we would need a precise
plan before making the collaboration formal.
This does not stop us from collaborating on the literature review,
methodologies, and least problematic points in the meanwhile.

Best regards,
Denis

On Thu, 15 Feb 2024 at 14:40, Gordijn, J. (J) <j.gordijn at vu.nl> wrote:

> Denis,
>
>
>
> I think this requires an update in the consortium agreement.
>
> In the current agreement, we have ruled out everything that had to with
> associate partners because there were not their.
>
> We have to think ourselves what we want to add to the agreement, regarding
> the point, and likely other issues that you mention.
>
>
>
> Best,
>
>
>
> -- Jaap Gordijn
>
>
>
> *From:* Denis Guilhot <dguilhot at bmat.com>
> *Sent:* donderdag 15 februari 2024 14:37
> *To:* Gordijn, J. (J) <j.gordijn at vu.nl>
> *Cc:* allpartners.music360-beta at listserver.vu.nl
> *Subject:* Re: [Allpartners.music360-beta] Visit Gema to Amsterdam
>
>
>
> Dear Jaap,
>
>
>
> Thanks for the meeting, it was very interesting.
>
> As we mentioned, we have no issues about GEMA joining as associated
> partner, all the opposite, I think it can strengthen the work and will
> definitely look good that such a company wants to join with 0 funding.
> Nevertheless, we would recommend discussing further with them the
> objectives and benefits for each party so we can define what the associated
> partnership would look like. Because for instance the data they have
> collected could not be disclosed within the Music360 project, since they
> only have access to part of the data, and under NDA. So what do you think
> about defining their role and part in the project before formalizing the
> collaboration? Obviously we can consult the project officer in parallel.
>
>
>
> Best regards,
>
> Denis
>
>
>
>
>
>
>
> On Thu, 15 Feb 2024 at 13:53, Gordijn, J. (J) <j.gordijn at vu.nl> wrote:
>
> Dear all,
>
> Today, the German CMO on author rights, GEMA, visited us, the VU team,
> plus a representation of BMAT.
> As I explained already earlier, there is significant overlap between the
> study that GEMA undertakes and what we do, specifically on the research of
> the value of music in retail and gastronomy.
> We both think it is a good idea to explore if we can formalize the
> relationship, for example by means of an associate partnership.
>
> The process for that is the following:
> 1. please let me know before feb 23rd, if you have any objection
> 2. if everyone agrees, I will consult the project officer about this.
> 3. If the project officer is positive, we will start the process of
> entering the associate partnership, which require a change in both the
> grant and consortium agreement. We all should agree, and the same holds for
> GEMA.
>
> Best,
>
> -- Jaap Gordijn
> UNESCO chair Decentralized Information Society Engineering
> Associate Professor VU Amsterdam, The Netherlands
> CEO The Value Engineers, The Netherlands
>
> ---------------------------------------
> Download the new e3value user manual at
> https://www.thevalueengineers.nl/the-e3value-user-manual/
>
>
> _______________________________________________
> Allpartners.music360-beta mailing list
> Allpartners.music360-beta at listserver.vu.nl
> https://listserver.vu.nl/mailman/listinfo/allpartners.music360-beta
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://listserver.vu.nl/pipermail/allpartners.music360-beta/attachments/20240215/3f827c69/attachment.html>


More information about the Allpartners.music360-beta mailing list