Hitting the Apply button in Commons twice shows message that site is already approved. At that stage, it is in the db, but not approved.

Two parts.

First, make sure that when data is sent the relation is set to reflect the privacy of the original record -- public collections and exhibit-stuff sets relation public. reverse for private.

Second, when records are updated send the privacy status and update accordingly.

Also requires work in the exporter

Search for sites by

• Site name
• Affiliation
• Admin name

The links built by SBM are relative, so when the HTML arrives at the Commons it tries to produce links that don't work.

For that matter any HTML content is likely to be problematic

this error in admin/items/edit:

In left column, where the metadata tabs are:
Warning: Invalid argument supplied for foreach() in /websites/devsites/sbrennan/onefive/admin/themes/default/items/form-tabs.php on line 51
In right column where form is:
Warning: Invalid argument supplied for foreach() in /websites/devsites/sbrennan/onefive/admin/themes/default/items/form.php on line 49

Institutions with multiple sites need to have a way to group them together, with just name and description.

I used "title" in the column, where collections has 'name'

Kinda annoying that I built it so that approved isn't a boolean. It's whether or not there's a date in the approved column.

I think I wanted to do this via record relations in case sites are using either CollectionTree or MultiCollections (if it ever gets really released)

Each group on the 'Browse Groups' view should probably have a link/button to allow the user to join the group, to save them a click if they don't need to go to the group profile page to know they want to join.

I'm wondering if the 'Join Group' button should be present even when there isn't a signed in user. New visitors would gasp at a glance what you can do with groups on that page, and clicking on the button would prompt them to create a user account.

Now it just uses an explicit for-each loop. For consistency, it'd be better to use Omeka's loop_records mechanism

• Site name
• Affiliation
• Admin name

I realize that Groups is its own plugin repository—should I be putting groups-related issues there? Also I want to make some Commons-only changes to the markup. I could make overriding views in the Commons theme, but I wouldn't get updates to the default group plugin views. How should we go about this?

• Browse sites
• Browse site organizations
• Single site view

Each time the import/update happens, a duplicate tagging is added

Also, the item gets imported anyway!

I wanted to start working on the Sites/show view, but I realize that I should probably add a site to the commons in order to come up with my own staging content. How do I do this? Also: once I add a site, where is the logo for the site set? Does the Commons pull the logos from the theme settings?

Exhibit functions specify the class to pass in, Exhibit, but I'm passing in SiteContext_Exhibit

Possibly useful information:

• embedded items
• items added to groups
• groups that use items
• statistics (a Commons 2.0 thing IIRC)
• Administrative work for the Commons administrator (TBD)

Needs input/meeting with @sheilabrennan and @sharonmleon