digicademy/academy

TYPO3 extension for creating research portals: Projects, Persons, Organizational Units, News, Events, and Media

Academy Current Research Information System (CRIS)

About

The "Academy" extension implements a framework for creating Current Research Information Systems (CRIS) with TYPO3. At its core it features a data model closely aligned to the CERIF standard and the OpenAIRE Guidelines for CRIS Managers. The extension can be used as a foundation for creating web based research information portals and databases with projects, persons, organizations, research products, news, events etc.

The extension has been in development by @digicademy since 2011 and is actively used as a basis for several CRIS projects of the Academy of Sciences and Literature | Mainz in cooperation with many partners:

• Academy of Sciences and Literature | Mainz
• A European Gateway for the Academies of Sciences and Humanities (AGATE)
• Portal of Rare Disciplines
• NFDI4Culture - Consortium for Research Data on Material and Immaterial Cultural Heritage

TYPO3 compatibility

Version	TYPO3	PHP	Support
current	9.5 - 10.4	7.4	Features, Bugfixes, Security Updates

Research Software Engineering

This software is licensed under the terms of the GNU General Public License v2 as published by the Free Software Foundation.

Author (2011-2022): Torsten Schrade | Academy of Sciences and Literature | Mainz

List of contributors (ideas and codewise):

• Baris Altun
• Aline Deicke
• Anna Neovesky
• Frederic von Vlahovits
• Frodo Podschwadek
• Julia Tolksdorf
• Julius Peinelt
• Linnaea Söhn
• Sebastian Lange

academy's Issues

Relations between CRIS entities (OrgUnits, Events etc.) and news display wrong label for news record

Description

When displaying relations between news and other CRIS entities in the backend the IRRE label for the news records is wrong

Steps to reproduce

Create a relation between any CRIS entity and a news record

Expected behaviour

The news label should be displayed correctly

Solution

This is due to a difference in the data structure during processing with \Digicademy\Academy\Utility\Backend\LabelUtility. BackendUtility::getRecord() fails for news records since the internal relation to tx_news_domain_model_news is an array rather than an integer (which is the case for all the other CRIS records).

Add listBySelectionAction to PojectsController

To enable also the selection of specific projects a listBySelectionAction should be added to the ProjectsController.php.

Gender attribute of persons should be also removed in 10.4-comp

The gender attribute of persons should be also removed in branch 10.4-comp. PR will folllow immediatly.

Slugs

Speaking path segments should be generated automatically and be editable via a slug fields in the backend. For further processing they should be properties of the domain objects.

Introduce possibility to add content elements to all CRIS entities

Enhances description of entities

TCA Migrations for TYPO3 11.5

Migrate TCA definitions for all CRIS entities to comply with latest specification for TYPO3 11.5. Especially take care of:

• Image fields for all CRIS entities with crop wizard
• makeCategorizable for all CRIS entities (move from ext_tables.php)
• l10n_mode seettings
• Role restrictions

Introduce field role restrictions for proper display in BE

Add products, publications, services entities

Introduce remaining CERIF main entities

gender attribute for persons is male by default

The gender attribute for persons is male by default. There are two possibilities from my perspective:

1. remove the ability to store gender information for persons in general by customizing the domain model, ext_tables_sql and TCA. A DB update would then be required. The stored information will be lost.

2. set the attribute to "Not selected" by default by customizing the TCA. Then the stored gender information in tx_academy_domain_model_persons must be modified by DB updates in running instances of tx_academy:

UPDATE tx_academy_domain_model_persons SET gender = 3 WHERE gender = 2;
UPDATE tx_academy_domain_model_persons SET gender = 2 WHERE gender = 1;
UPDATE tx_academy_domain_model_persons SET gender = 1 WHERE gender = 0;

However, the gender information should be removed from the Persons/Show.vcf.