Wish List

From ResourceSpace Documentation Wiki

Jump to: navigation, search

Add your suggestions below.

Note that there is currently no unpaid development time going in to ResourceSpace. This page serves as a place to pool ideas and for developers to add cost estimates. In the event that voluntary developers come forward this list will also be used to consider items for inclusion in a road map.

Please don't add items to this list with the expectation that they will then be developed.

  • User-editable adressbook which works with the new AJAX auto-fill field for storing frequently used external e-mail recipients.
  • Ability to configure the reply-to adress for Collection/Resource e-mail links so the reply goes directly to the user who sent it. As it is today, all replies goes directly to the system e-mail adress, usually something like "somecompany@somecompany.com" or "webmaster@somecompany.com". Lots of recipients press the "reply-to" button on the assumption that the reply will go directly to the person who sent the link/message, but in this case the message will go to any number of people who are set up to receive company e-mail. If the reply contains any personal messages this could potentially lead to some embarassment. The other option is to configure "no_reply@somecompany.com" as the system e-mail adress - but this will cause delays before the sender receives an "undelivered mail" message and and extra workflow steps as the recipient re-sends to the senders real e-mail adress. So this is hardly ideal. If auto-setting the users reply-to adress in the mail header itself is difficult, maybe a workaround could be to write a message footer with a message like "This is a system-generated message, to contact the sender directly use the adress "john@somecompany.com"", where the e-mail adress is inserted as a field variable, pulling the senders e-mail adress from the db.
  • Sortable lists in list view
  • Add col image to popup infobox in list view only.
  • An 'X' remove icon in the ´Show all´view of a Collection (similar to the one which is available in the usual Collection 'dock')
  • Tabs for the resource upload page too, not just the resource view page
  • "Retiring/archiving" Collections so they disappear from the active Collections view - but still allows for any previous Collections and their associated e-mail/download links to remain active. Currently Collections must be kept "alive" to enable users to access e-mail collection links weeks after they were originally sent out. If those Collections are deleted, then all e-mail links to go dead. Instead of keeping them open, cluttering the current "workspace", it would be nice to "archive" them/put them into a "passive mode" or whatchacall it, so they disappear from the current list but are still accessible - simply hidden away from normal/active view.
  • AJAX auto-complete for the Collections search field
  • Improved documentation in reguards to php components and php.ini configuration for those who aren't as familar with php
  • Admin "Group mode": A switch whereby Admins can switch between children groups, all operations and all resources/content which shows is related to the chosen group. All alternatives concerning other groups (e-mail recipient lists etc) will be hidden (makes for a less cluttered and confusing interface. Think Fast user switching or Spaces in Mac OS X.) [maybe a 'log in as this user' or 'emulate user' option ~Dan][Yes, that sounds like the best way to go. Morten]
  • LDAP Authentication / Microsoft Active Directory [some organisations possibly willing to fund]
  • Support for MS Office documents (probably best to develop as a plug-in using a commercial library if an open-source library can't be found?)

{note this is done in other projects by using OpenOffice.org running on the server to render previews - Sollos} Suggested solved by using QuickLook on Mac OS X Leopard servers. -> OpenDocument (OpenOffice Calc, Draw, Writer, and Impress, and Math Formulas) and OOXML (Office 2007 docx,pptx,xlsx) office formats are now preview-supported. -Tom

  • Improved permission & rights management: all groups can see every resource; resource has 1 or more owner groups (with different priorities); download is freely permitted only to owner group; for other users the resource is locked; to download a resource, the user must ask for permission to owner; the owner can grant the permission for resource/user for a limited time period (ie 30 minutes) (Willing to fund - Camillo@Mediaset) [I don't understand this as we already have fine-grained permissions via the 'custom' access level ~Dan]
  • Localizable Theme titles (perhaps by using ~en:Norway~no:Norge variables)?
  • Maintain Version history or "stack" of previous versions of an asset.
  • New "asset" concept: an asset is a new abstract entity resource which act as a container for different resources; for example video (as different format of the same file - ie hq, lq), images (as different formats - ie jpeg, tiff), or a combination of mixed resources (Camillo@Mediaset).
  • "Keep me logged in at this workstation" - pop-up alert warning a user not to check it if using a public terminal
  • OpenID support (http://openid.net) - perhaps by using PrefPass?: "Adding PrefPass to your site is as easy as can be. You just sign up, enter your site details, and then paste some code on your registration and login pages. Instantly, your users can use IDs from Yahoo! to AIM to Facebook to OpenID." (http://about.prefpass.com/site-owners)
  • Client Selection Gallery - a simple preview gallery to allow clients or designers to make selections from photoshoots. Photographers upload lo-res versions of photos. Selections made easy with checkboxes and an e-mail feedback form complete with a file list - a bit like in this example: Adobe Lightroom selection webgallery
  • "Inherit settings from group"-option to simplify/speed up MU administration across different user levels within a client group. All "f" and "j" permissions are inherited from the "parent" group (usually admin/superuser level within a client group)
  • Remember tab selection - if tab "Description" was the last one selected, when going to the next resource the same tab should remain the default/topmost tab

Downgraded items

  • Support for selecting multiple resources at a time by shift-clicking or control-clicking like in desktop apps [I don't think this is necessary, as collections are the RS way to select resources ~Dan]
  • Support for drag-and-drop from main window into Collections [not possible to do this due as they are separate frames ~Dan]
Retrieved from "http://rswiki.montala.net/index.php/Wish_List"
Personal tools