v4.0.0-rc1

This makes the module compatible with Omeka S 4.0.x and adds new features and fixes bugs.

What's Changed

*Update item sets to use add/remove/current parameters @alexdryden in #127

• Restore views for site resources and site users by @alexdryden in #129
• Include option to bypass team filter on browse views for global admin @alexdryden in #131
• Improvements to user management panel for team users by @alexdryden in #132
• Show global admins teams where they are not a member in team select form elements (bd22350)
• Fix issue on user form that prevented non-global admins from making changes to their current team (44d7049)
• Implement Search API action for all Team Entities
• Filter user browse pages by team (b67f19f)
• Various updates for form fields and redirect behavior after form submission to support automated acceptance testing
• Update views to use dl format introduced in 4.x (4f975e3)

Full Changelog: 3.2.0-1...v4.0.0-rc

3.2.0-1

What's Changed

• Address bugs related to #100, #101 that caused teams to be removed but not added when processing edit requests for resources
• Internal version number synced with release tag. Previously, github release tags represented the latest version of Omeka that the module had been tested against, and module version in module.ini represented the Teams semantic versioning.
• Update module.ini by @mquantin in #114
• Update proxies with getTeamAsset() function by @alexdryden in #120
• Issue 121 by @alexdryden in #124

New Contributors

• @mquantin made their first contribution in #114

Full Changelog: v3.2.0...3.2.0-1

v3.2.0

What's Changed

We've added support for the Collecting module so that items generated by the visitors will be added to the appropriate teams based on the site's team membership. Thanks @tatipovo for the report.
We've also cleaned up the REST API so that it provides appropriate messages and removed some legacy artifacts. For the REST API you can now:

• query team_resources by team to see all of the team's resource or by resource id to see all of the teams where the resource is a member. Note: Because Team Resources are essentially a join table, they don't have incremented ids (they have a composite id of the team_id and resource_id). As such, there is no way to use the REST API to find a specific team resource.
• Query team Get a more detailed picture of what assets, resource, sites and users belong to the team. Depending on the size of your site, this might be an expensive call.

This also fixes an issue where team assets weren't added to teams through the Add Team or Edit Team forms. Thanks @mquantin for the report.

See a summary of the issues address.

• Issue 94 by @alexdryden in #95
• Add collecting to teams based on associated site's teams by @alexdryden in #96
• Handle cases when user has no team and selects "Change Team" by @alexdryden in #98
• Makes the fix for list-of-sites reachable by moving REST catch by @alexdryden in #99
• Issue 100 by @alexdryden in #101
• Don't show site options on edit form by @alexdryden in #102
• Correct count on form field @alexdryden in #103
• Authority plugin refactoring by @alexdryden in #106
• Get user assets for update and create by @alexdryden in #111
• Api cleanup by @alexdryden in #113

Full Changelog: v2.1.2...v3.2.0

v3.1.0-8

What's Changed

• Fix item_site issue with CSV Import by @alexdryden in #86
• Fix uninstall by @alexdryden in #89
• Fix install by @alexdryden in #88

Full Changelog: v3.1.0-7...v3.1.0-8

v3.1.0-7

This is the 7th patch developed on the Omeka-s 3.1 branch. It has gone through some incidental testing on 3.2, but is recommended for 3.1.

What's Changed

• Issue 82 by @alexdryden in #84
• Fixes a bug where sites with more than one team were not properly filtering items for site blocks that accept query parameters (Map by query and Browse preview)
• Display of query parameter UI elements for Browse by preview and Map by query were not being rendered when the page edit view was first loaded.

Full Changelog: v3.1.0-6...v3.1.0-7

v3.1.0-6

What's Changed

• Issue 78 by @alexdryden in #79
• Add user's currrent team to resource templates that are imported by @alexdryden in #80
• This corrects a previous defect in the attached .zip

Full Changelog: v3.1.0-5...v3.1.0-6

Team Manager Patch v3.1.0-5

What's Changed

• Fix Issue 58 by @alexdryden in #61
• Show site user and site resource form to global admins by @alexdryden in #63
• Issue 64 by @alexdryden in #65
• Update global setting with config by @alexdryden in #67
• Issue 68 by @alexdryden in #69
• Update the default sites for items when first team is added by @alexdryden in #71

Full Changelog: v3.1.0-4-beta...v3.1.0-5

Team Manager

Restores the ability for team members with the appropriate role permissions to manage some aspects of the team, including:

• Add and remove team members
• Change team member roles
• Change team name and description

Full Changelog: v3.1.0-3-beta...v3.1.0-4-beta

v3.1.0-3

Full Changelog: v3.1.0-2...v3.1.0-3-beta

This integrates assets into Teams. On upgrade, assets will be added to whichever team(s) the item/site they decorate belongs to. For new assets created after the upgrade, assets will be added to the users current team.

v3.1.0-2

Features/Changess:

Refactoring views to conform to PSR-2 standards and cleaning up
Add option to disable Supervisors from making new users
    -See #55 
Ability to change teams from within the team list
Disable views for site level management of resources and user
    -User permissions in a site and a site's collection of items are managed by teams. So we are hiding these views to prevent confusion.