To increase the visibility of sponsorship of digitisation projects we would like to display some attribution information on the Data Portal. To avoid depending on a full-scale attribution model being sculpted into EMu (though this would be the ideal way of doing this) we will attach sponsorship information to project codes. This will allow us to expose the data in 3 ways:
On record pages, simply just display a logo and a name
On a dedicated sponsorship page, with a list of logos and names
In a visualisation (probably a treemap) showing the areas that have been funded for digitisation and by who
This sponsorship work was requested by the development team and therefore has a corporate focus, however, we will also show sponsorship data where more traditional academic sources have provided funding, such as NERC for example. This kind of attribution is typically required in other academic outputs and the Data Portal should not be an exception.
Note: this feature has been provisionally brought forward into this roadmap from the 2019-2020 roadmap with the intent to determine what work should be undertaken. There were significant questions raised which paused the work in the last roadmap and many of these have not been properly addressed yet. The work on this feature should start by ensuring the scope and aims are fully outlined and understood before design and implementation begins.
Overview
To increase the visibility of sponsorship of digitisation projects we would like to display some attribution information on the Data Portal. To avoid depending on a full-scale attribution model being sculpted into EMu (though this would be the ideal way of doing this) we will attach sponsorship information to project codes. This will allow us to expose the data in 3 ways:
This sponsorship work was requested by the development team and therefore has a corporate focus, however, we will also show sponsorship data where more traditional academic sources have provided funding, such as NERC for example. This kind of attribution is typically required in other academic outputs and the Data Portal should not be an exception.
Note: this feature has been provisionally brought forward into this roadmap from the 2019-2020 roadmap with the intent to determine what work should be undertaken. There were significant questions raised which paused the work in the last roadmap and many of these have not been properly addressed yet. The work on this feature should start by ensuring the scope and aims are fully outlined and understood before design and implementation begins.