Re: [Codematch-develop] Codematch Call Wed 13 May

[Christian O'Flaherty <[e-mail]>]

Hi Lisandro,

> 
> I understand your point. However, I believe it’s a matter of, let’s say, how the “workflow” of a documento>Request>Implementation is understood. My reading, from all our discussions, is the following:
> 
> 1) There are several documents (I-Ds, RFCs, etc.) available;
> 
> 2) Someone (e.g., group chair) needs the development of some code for one or more documents related to one another. The group chair then creates a CodeRequest in the system, linking that request to the document(s) he/she wants someone else to code. A mentor is assigned to this CodeRequest as well. In the current data model, a CodeRequest is materialized by creating a new ProjectContainer as well as a new CodeRequest linked to that container;

Agree 100%

> 3) Developers interested in coding for a specific, advertised CodeRequest associate their projects to that CodeRequest by creating a CodeProject in the data model. Notice however that the set of documents that the new projects will code is inherited from the original CodeRequest (linked in the data model to the code request’s Project Container entry). It means that the set of document is something handled at the Project Container, instead of at the CodeProject.

This is correct, but the same program can implement something else (not related by the same code request). The table CodeProject will be populated by programers and we don’t want to “limit” their efforts to a single code request and we want to “capture” as much as possible on our database. 

> 
> My understanding is that allowing a single CodeProject to be linked to several ProjectContainers will create confusion.
> We wanted “comparable” CodeProjects that could related to the same sets of documents. That is achieved by linking these projects to the same ProjectContainer. That’s why I still believe the relationship here is still a many (Code Projects) to 1 (ProjectContainer).

We will be able to compare them exactly the same way because that relationship from one CodeProject to several documents is kept. 

I agree that it is confusing (that’s why I suggested to have one to one initially) , but I think those relationships are capturing different information.

Christian 

> 
> Best regards,
> 
> Lisandro
> 
>>> 
>>>> - A “CodeRequest” is an extended container, adding estimated LoE information. 
>>>> 
>>>> 
>>>> 
>>>> <codematchv5.png>
>>>> 
>>>> Best regards,
>>>> 
>>>> Lisandro
>>>> 
>>> 
>> 
>