Closes #2547 Add ability to customize publication types.

[trackleft]

Description

Adds a new configurable entity type called 'publication type'.

Adds a core patch from a merge request on issue #3347343

Creates a mechanism where site owners can create arbitrary publication types and map them to supported types in citation style language

This way the list of types is editable for both the field on the publication content type and within views with exposed forms for filters.

Adds a new configuration entity for each supported type. See the article type as an example

Related issues

Closes #2547

How to test

Enable az_publication
Add a new publication
Select Article in Book as the type.
See what happens.

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Allows changing the filter from something like.

To a more manage-able

[trackleft]

Looks like this PR works as expected, with no change in the output, and just an additional option in field_az_publication_type and we can filter on it in the search view.

[tadean]

The options currently listed for the type are from the Citation Style Language Standard. This type field is used to determine what special cases are used in the style rendering. I'm not sure if this will cite books correctly...I think many styles will treat this as a generic type that doesn't meet any of the checks for types that have specific rules associated with them.

Are the publications in question a collection/anthology? Those are typically cited as Book but with a container (Ordinarily books do not have a container)

I've wondered if maybe we need a layer of abstraction from the types a visitor sees versus what's presented to the CSL processing (perhaps a taxonomy vocabulary that lists what types are available on the site, with a field for a mapping for what CSL type they actually use). This would allow for arbitrary names for the publication types maybe...

[trackleft]

There can be a follow-up to integrate draggable list builder https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Config%21Entity%21DraggableListBuilder.php/class/DraggableListBuilder/9

[tadean]

Does switching to DOM-based parsing here resolve an issue with the current regex-based parsing?

[trackleft]

I'm not sure anymore, but line 309 says not to parse HTML with regex.

[tadean]

Is this an intended change?

[tadean]

Currently in the view, it seems like field_az_publication_mapped_type_target_id is showing up as a broken handler:

[tadean]

Currently in the view, it seems like field_az_publication_mapped_type_target_id is showing up as a broken handler:

This was a local build problem for me, disregard sorry. I was testing the database update by upgrading a site from a previous version and composer hadn't yet applied the patch for the entityreference filter.