Node views data: Several oddities

I don't know if there is another issue or not, sorry.

What we did for some of the other duplicated fields that appear in more than one table, such as Language fields, si we changed the Title and Description of these based on which table it is in. This is in EntityViewsData, for instance:

  protected function processViewsDataForLanguage($table, FieldDefinitionInterface $field_definition, array &$views_field, $field_column_name) {
    // Apply special titles for the langcode field.
    if ($field_definition->getName() == $this->entityType->getKey('langcode')) {
      if ($table == $this->entityType->getDataTable() || $table == $this->entityType->getRevisionDataTable()) {
        $views_field['title'] = $this->t('Translation language');
      }
      if ($table == $this->entityType->getBaseTable() || $table == $this->entityType->getRevisionTable()) {
        $views_field['title'] =  $this->t('Original language');
      }
    }
  }

We may just need to do this more generically, for any fields that are duplicated between base table and data table. Either that or maybe remove duplicated fields from the base table if they also appear in the data table, aside from Language, which actually has a different meaning on each... but things like Node ID and Content Type don't.

Either that or we will have to do it case-by-case in the specific *ViewsData classes. :(

Indeed. (2) was fixed in the base class by removing the dups, and (1) was fixed on the issue mentioned in #3. So really this is a duplicate.