Ability to customize the reports, for example, to add filter to show Group name

Writing the code it would take to make the reports customizable is not on my roadmap, but I am using out-of-the-box Drupal tables to store the records, so I should be able to (eventually) add the ability to browse the data with custom views.

In the meantime...I suspect you could just install Views Custom Table → and be good to go. You would need the machine names of my tables, which are listed in the .install file. Skimming through the docs, it looks like it can even map my UID column to Drupal's UID column, which would let you add your Groups relationships.

Thank you so much, I'll report to my team and try it.

Dear John Jameson

I followed your suggestions, I was able to link to the groups on your editoria11y_dismissals table, because there is a uid in that table.
Thank you so much.

But there is no uid in the editoria11y_results table, so I can't do the same thing there.

Do you have any plan, or is it a reasonable request to add uid to the editoria11y_results table ?

Best regards,

Xingwu Chai

I generally think of results as "userless," since they map to content.

That said -- if different users have access to different parts of your site -- Removing Results When a Node is Deleted ✨ Remove entry when page is deleted. Fixed will require adding a NID -- would that let you map the NID to the users or groups that have access to it?

Great, that will work for us.

When will this be released ?

Best regards,

Xingwu Chai

Checkout #3380446 ( https://www.drupal.org/project/editoria11y/issues/ → )

We added views support for the reports. Next step would/could be to rewrite the export handling to use views exports, that way we are no longer limited to CSV but can also export json, xml,....

Related issue is finished; working on some other code I want to wrap in with this, and then targeting an October release.

Entity ID added in 2.1.0 → .

That said: the entity_id field is not always a NID -- sometimes it is a taxonomy TID, eventually it may also include a UID (for user routes) -- I'm using it in tandem with my route_name field to keep track of changing aliases and entity delete hooks.

So: straightforward/direct Joins between my tables and the Node table will not work without filtering first to a single route name (entity.node.canonical), at which point the remaining rows with non-zero entity IDs could be used to grab the UID of the author/editor and their group info from the Node table.

I am not currently planning to duplicate the author+editor UIDs into my tables, in hopes that someone can help me set up those Joins at some point in the future, to keep my tables a little leaner.

Since I'm not planning to work further on this...I'm going to close this issue for now. If anybody wants to contribute I'll happily re-open, review and integrate!

Automatically closed - issue fixed for 2 weeks with no activity.