Featured Collections - some thoughts and questions.

[Jeffrey Rickeard]

As a new user, I had some initial trouble assigning a collection as a featured asset. They are advertised well with their own tab in the header, but until a collection was made public, there are not many clues about how to quickly create them. As an alternative, I was wondering if it would be possible to have the option to assign a collection as featured, with a warning that the assets will be made public?

Can you have a featured collection within a user group or among multiple users within a project without making the collection public? It still seems valid to feature a collection privately within a project context, but admittedly there are other very good options to share collections.

Category names are quite disposable and since they are just a quick word or two this seems appropriate, but the process to add the name appears quite elaborate with a drop box and second entry field once one has been created. The pulldown lends itself to having a saved list of names (maybe even some built-in) but this is not done. Was there any thought on doing this?

Lastly, When creating a featured category it seems only necessary to select public and add the category name to have it saved, i.e. does not require you to commit with the save button. This is also true for the removal process and will delete the featured collection and category name without warning, just by selecting "Private" in the access pulldown. Not a huge issue, but doesn't seem consistent with how changes are normally made within the edit environment.

Thanks.

Jeff.

[Allison M Stec]

Featured collections are a special kind of public collection. Perhaps some better language on the collection edit page would provide better guidance as to how to make a private collection into a public featured collection.

If you want to restrict featured collections by user groups you can have a look at the "j" permissions. These will allow you to hide featured collections by feature level.

Once a featured level is created it will reappear as an option in the dropdown on the collection edit page. If an option is removed and is not being used by any other featured collection, the label is removed. Is this not happening for you? While having default resource types and fields seems logical, I'm not sure a featured collection level structure could be that easy. In fact, I've never seen two installs use this feature the same way. Further, the way that featured collections are structured in the back end of RS would require restructuring to make this possible.

Editing resources is set to autosave (by default) so this behavior is actually quite similar.

If you haven't already had a look at the wiki and the knowledge base they're worth checking out:

http://wiki.resourcespace.org/index.php?title=Main_Page

http://resourcespace.org/knowledge-base/

--
ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.org
---
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
--
ResourceSpace Developer
Reseller of Colorhythm's Prismpoint Portal DAM

[Jeffrey Rickeard]

Thanks once again Alison.

The "j" permissions certainly address the featured collections access I raised. I made the assumption that if the collection resource was public, all access restrictions aside, then everyone gets the view. I obviously have many features yet to explore.

In answer to your query, the category name - or feature "level" as you describe - is working as expected and does appear in the pull down whilst the category remains in use.

I also take note that specific pulldown options in other edit menus undergo an autosave feature. The "saving ... saved" notification during and after the process does serve to alert you that the selection is now active.

The wiki and knowledge base are excellent resources as is the community, much appreciated.