I have been thinking (I know dangerous thing to do...) about how to manage different "categories" of gallery groups. E.g., having "Site" galleries (managed by multiple people and "owned" by the site) vs "Personal" galleries (managed/owned by users). Note that "Site" galleries might be also considered "Shared" depending on the scope of access permissions.

Obviously, the "Personal" galleries case is the NG default. The "Site" case can mostly be done via a new relationship, setting up "Site Gallery" and "Site Gallery Image" node types, then created the needed views and granting the correct permissions.

One thing that is hard to do is getting the navigation items right. E.g., listing just Site Galleries or Personal Galleries; getting the breadcrumb display right (e.g. Site galleries should NOT include links to "XXX's Galleries"); and the like.

One possible way I see to allow this would be to:

- add a "Gallery Listing Settings" section to the relationship settings form. This could have options to specify the menu information (title / short type name), a view to list this relationship, the listing page title, and some breadcrumb control options (e.g. Show owner/don't show owner).

- Have the hook_menu build an entry for each relationship that has menu information filled in (e.g. /galleries/short_type_name ).

This would allow you to create the Site relationship, specify a short type like "site" and then go to /galleries/site to see and navigate through all site galleries... while maintaining the default "personal" gallery behavior.

A longer term discussion is how to include the nodes and views needed to support "Site" galleries so people don't have to create the node types, views, etc... I'm thinking that node_gallery needs to have an API that allows "sub"-modules to programatically add relationships.

Hmm, a quick look at the code seems to indicate that this might not take a lot of changes. The Add A Relationship code is contained in the node_gallery_relationship_*_form_submit functions. It does not like it would be too hard to make them call a function(s) with values from the forms. This function(s) would be the API function for external modules to "add a relationship" programatically.

Just some thoughts I'd wanted to throw out for possible discussion/consideration.

Comments

justintime’s picture

This is going to be implemented in node_gallery_access as a "shared" gallery. See http://drupal.org/node/606064

justintime’s picture

Status: Active » Closed (won't fix)

Marking won't fix since NGA will take care of it.