v4.1.0-2 patch

This includes a few updates to the rest api coverage, some quality of life fixes, and some refactoring.

What's Changed

• Api abstraction by @alexdryden in #184
• fix: allow all users to see team roles by @alexdryden in #185
• Issue 186 by @alexdryden in #187
• Fixes a bug where team assets were not being displayed in the admin interface.

Full Changelog: v4.1.0-1...v4.1.0-2

Note: the v4.1.0-1 tag was accidentally used in one of the v4.1.0-<pre-release>, so using tag v4.1.0-2.

v4.1.0

TL;DR

This release adds features to help on-board the module for existing installations:

• Add items to teams via bulk add/edit
• Use query selector to add items to teams via Add new team and Update team
• Allow users other than global admin to use the bypass team filter feature

Special thanks to @rachelericceri and colleagues for their contributions in the issues.

What's Changed

• Remove checks for "super" global admin by @alexdryden in #150
• Fixes #146 by waiting to flush till after validataion by @alexdryden in #151
• I152 by @alexdryden in #153
• Api create team reasource by @alexdryden in #155
• Update admin menu for 4.1 changes by @alexdryden in #156
• Issue 157 by @alexdryden in #159
• Issue 158 rebase by @alexdryden in #167
• V4.1.0 rc2 rebase by @alexdryden in #168
• Bypass teams filter team resouce population by @alexdryden in #171
• fix: eliminate log clutter from various benign sources by @alexdryden in #176
• fix: add bypass team filter to the Advanced search by @alexdryden in #177
• Batch delete all by @alexdryden in #179
• fix: add data-collection-action attrib. to send data into pipeline by @alexdryden in #181

See 4.1.0-rc# for more details.

Full Changelog: v4.0.1...v4.1.0-1

v4.1.0-rc4-beta

• fixes an issue where bypass_teams_filter wasn't added in cases where the Query controller was calling the Query element
• BREAKING CHANGE: changes how team permissions are interpreted so that users with site permissions in their team aren't prevented from deleting the team.
• add returnScalar capability to team-site api endpoint
• add site syncing to delete/create api for team-resources as well as the updateTeamResources Job

Full Changelog: v4.1.0-rc3-beta1...v4.1.0-rc4-beta

v4.1.0-rc3-beta1

Purpose

This release is ready for beta testing and automated integration testing

What's Changed

• V4.1.0 rc2 rebase by @alexdryden in #168
• Fix #170: Bypass teams filter to populate advanced search element options by @alexdryden in #171
• fix: eliminate log clutter from various benign sources by @alexdryden in #176
• addresses #174, #175: add bypass team filter checkbox to the Advanced search by @alexdryden in #177
• Fix #172: Add coverage for Batch function Delete All, in Batch delete all by @alexdryden in #179
• Fix #180: add data-collection-action attrib. to send data into batch update all pipeline via preprocessing by @alexdryden in #181

Details

Fix #170:
From the pr:

This fixes #170 by replacing advanced search elements with ones that have the bypass_team_filter query parameter. The design of this approach is that the flag is neutered if the user is not authorized to have access to the bypass, so users without this ability will have the same experience with the standard advanced search.

However, this does grant these same expanded options for the regular Advanced Search for users with the authority to bypass team filtering. My feeling is that this is a positive externality and we don't need to do anything additional to maintain the old behavior or the standard advanced search form.

fix #174, #175:
The preview function was working properly and displaying no results because the constructed query always lacked the bypass_team_filter flag. This fix adds an option to the bottom of the form to bypass the teams filter if the user's core Omeka role is among those who have access to that feature.

fix #172:
The batch support had previously only included Batch Delete Selected. This add support for Batch Delete All by redirecting the batch-delete-all route to the Teams Index controller where a soft delete (to Trashcan) is performed.

fix #180:
Batch Update all differs from Batch Update in that it goes through a complex data preprocessing step that funnels form responses into buckets based on the action indicated. In order to make it through this filtering, elements should indicate which bucket they belong to in a data-collection-action attribute. In practice, it doesn't matter which bucket you put your module's data into unless it is structured in such a way that it will be handled by the batch updated. If you plan to intercept your data and complete the action in the module then you can select any bucket.

Full Changelog: v4.1.0-rc2...v4.1.0-rc3-beta1

v4.1.0-rc2

Full Changelog: v4.1.0...v4.1.0-rc2

Fixes/updates from rc1:
Fix: add item media when adding items by using the 'recursive' flag
Feature: Allows recursive adding and deleting of items inside item sets
Fix: includes the secondary resource form on Team Add views
Fix: modifies form labels for clarity
Fix: don't group value options for team create because everything will be "not in team"
Fix: hides the form element that is used to collect which secondary resources have been removed from a team via the Team Update view
Fix: Set global admin as able to use the bypass teams filter on install

v4.1.0-rc1

What's Changed

• Update admin menu for 4.1 changes by @alexdryden in #156
• Issue 157 by @alexdryden in #159 (@rachelericceri)
• Issue 158 rebase by @alexdryden in #167 (@rachelericceri)

This primarily addresses issues 157 and 158 by adding the following user facing feature:
Adding a config setting so admins can control who can use the Bypass Teams Filter feature
Adding Teams as an option for bulk edits
Reconfiguring the Team Edit interface to use a query for items and chosen select for Resource Templates and Item sets

Full Changelog: v4.0.2...v4.1.0

v4.0.2

What's Changed

• Remove checks for "super" global admin by @alexdryden in #150
• Fixes #146 by waiting to flush till after validataion by @alexdryden in #151
• I152 by @alexdryden in #153
• Api create team reasource by @alexdryden in #155

Full Changelog: v4.0.1...v4.0.2

Omeka v4.x

What's Changed

• Update module.ini by @mquantin in #114
• Update proxies with getTeamAsset() function by @alexdryden in #120
• Issue 121 by @alexdryden in #124
• Integrate fix into 4.x testing by @alexdryden in #127
• Restore views for site resources and site users by @alexdryden in #129
• Issue 130 bypas team filter by @alexdryden in #131
• User management by @alexdryden in #132
• V4.x by @alexdryden in #133
• Prevent from trying to add bypass filter to public views by @alexdryden in #135
• Use countable object by @alexdryden in #136
• Issue 138 by @alexdryden in #140

New Contributors

• @mquantin made their first contribution in #114

Full Changelog: v3.2.0...v4.0.1

v4.0.0-rc3

This fixes a bug that caused user checks on public views

Full Changelog: v4.0.0-rc2...v4.0.0-rc3

v4.0.0-rc2

Fixes an issue where items where removed from site-item upon editing the item if the item belonged to only one team

What's Changed

• V4.x by @alexdryden in #133

Full Changelog: v4.0.0-rc...v4.0.0-rc2