Improve the definition of the cfProj entity

[jdvorak001]

No description provided.

[jdvorak001]

We start from:

A project in business and science is typically defined as a collaborative enterprise, frequently involving research or design, that is carefully planned to achieve a particular aim. Projects can be further defined as temporary rather than permanent social systems that are constituted by teams within or across organizations to accomplish particular tasks under time constraints.

Definition Source: http://en.wikipedia.org/wiki/Project

[jdvorak001]

A possible usage note:

In the research information domain, one typically tracks research projects and projects that form or enhance infrastructure for research.
Many projects have a project plan that breaks down the activities into stages and/or work packages.

[abollini]

It could be useful to add a note about the difference between cfProj and cfFund.

It is important to note that the cfProj entity only capture details about the project plan and scope, funding information (i.e. received grants) are a separate entitity, see cfFund

[jdvorak001]

Yes, agreed. I'd just prefer not to use the physical names for entities in their definitions. So it could be something like:

It is important ot note that the Project entity only captures details of the project scope and plan. Information about the funding of a Project (i.e., the grants received) goes into the Funding entity.

[jdvorak001]

Outcome of today's virtual TG meeting:

A piece of planned work or an activity that is finished over a period of time and intended to achieve a particular purpose.
Source: http://dictionary.cambridge.org/dictionary/english/project

In the research information domain, one tracks research projects and projects that form or enhance infrastructure for research. Depending on the scope one can also track finer levels of granularity: stages, work packages, individual tasks. All such activities are also modelled using the Project entity.

It is important to note that the Project entity only captures details of the project scope and plan. Information about involved and needed resources to execute the project such as the funding of a Project (i.e., the grants received), the involved people, organisations, the supporting infrastructures goes into separate entities (the Funding entity, the Person entity, the OrgUnit entity, the infrastructure entities).
Output from the project can be linked using the appropriate entities.
Projects are different from OrgUnits in that they are temporary, rather than permanent social systems.

[jdvorak001]

A bit of additional smoothing applied, in bold:

A piece of planned work or an activity that is finished over a period of time and intended to achieve a particular purpose.
Source: http://dictionary.cambridge.org/dictionary/english/project

In the research information domain, one typically tracks research projects and projects that create or enhance infrastructure for research. Depending on the scope one can also track finer levels of granularity: stages, work packages, down to individual tasks. All such activities are also modelled using the Project entity.
Projects are different from OrgUnits in that they are temporary rather than permanent social systems.

It is important to note that the Project entity only captures details of the project scope and plan. Information about the resources needed to execute the project such as the funding of a Project (i.e., the grants received), the people and organisations involved, the supporting infrastructures, the outputs produced, etc. is contained in separate entities (the Funding entity, the Person entity, the OrgUnit entity, the infrastructure entities, the result entities) and is linked to the Project.