Define what researchers, administrative support and librarians need from projects in Biblio

[mietcls]

Enhancement

Define what researchers, administrative support and librarians need from projects in Biblio.

What do people look for? What information do they expect to see? Why?

[netsensei]

For reference, this is how a single project is currently modeled via the REST API:

{
    "id": "string",
    "created": "2023-12-19T10:09:09.791Z",
    "modified": "2023-12-19T10:09:09.791Z",
    "type": "string",
    "identifier": [
        {
            "type": "string",
            "propertyID": "string",
            "value": "string"
        }
    ],
    "isFundedBy": {
        "type": "string",
        "hasCallNumber": "string",
        "isAwardedBy": {
            "type": "string",
            "name": "string"
        }
    },
    "hasAcronym": [
        "string"
    ],
    "name": [
        {
            "language": "string",
            "value": "string"
        }
    ],
    "description": [
        {
            "language": "string",
            "value": "string"
        }
    ],
    "foundingDate": "string",
    "dissolutionDate": "string"
}

Few notes:

• The identifier field contains all the identifiers by which the project is known. The id field contains a "canonical" identifier taken from the identifiers field and formatted as an URN e.g. urn:iweto:AABB99.
• name and description fields are setup to contain multiple translations once we move the pipeline to direct updates from GISMO.
• IsFundedBy could be a jumping board for more background info regarding funding sources. Currently, it only contains either terse FP7 or H2020 data.