[
https://jira.duraspace.org/browse/DS-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-872:
---------------------------
Status: Open (was: Received)
This was discussed in Developers Meeting today:
[20:07] <kompewter> [ https://jira.duraspace.org/browse/DS-872 ] - [#DS-872]
Community-based feedback - DuraSpace JIRA
...
[20:09] <mhwood> 872 sounds sensible.
[20:10] <tdonohue> I'd be ok with 872 -- though I had never run into this in
the past, to be honest. What do others think?
[20:11] <PeterDietz> our feedback all goes to our repository-support-team's
group list serv
[20:11] <PeterDietz> ...they fan out any requests from there
[20:11] <tdonohue> yea, that's how we used to manage it as well, when I was at
U of Illinois -- it all went to a listserv
[20:11] <mdiggory> we've mostly focused on using the Community/Collection Admin
group to manage such emailing logic
[20:12] <hpottinger> I could see a use case for a shared repository for a
consortium, or a multi-campus university
[20:12] <mdiggory> I'd almost always suggest not adding yet another
"collection/community" mapping to the space c.fg
[20:13] <mdiggory> I'd rather see a Role "Feedback Recipients" and a
Groups/EPersons Attached to it in the DB somehow
[20:14] <mhwood> You mean: invent a "gets feedback" permission and grant that
to some group on some container? Interesting.
[20:14] <mdiggory> for instance, if we were to approach this in the XMLUI, we'd
create an aspect, model and db table to support the admin adding removing users
from the listing.
[20:15] <mdiggory> well, I know a "permission" is a bit of a stretch....
[20:15] <mhwood> It's what ACLs have.
[20:15] <tdonohue> yea, I like that idea, mdiggory. Either that, or just have
the option to send feedback to anyone who is in the Community Admin group or
Collection Admin group
[20:16] <tdonohue> well, any volunteers to work with this patch a bit? or
provide more detailed feedback in the comments on how to improve? It sounds
like the *idea* is sound, just that there are some concerns about the exact
patch
[20:16] <mhwood> ACL approach is kind of a backdoor way to make this into
container metadata.
[20:17] <robint> I won't have time pre feature freeze
[20:17] <hpottinger> we may play with the patch here in Missouri, would need to
see how the managers felt about it
[20:17] <robint> hpottinger: Please do. Any feedback very welcome
[20:18] <tdonohue> thanks hpottinger. Yea, just to be clear, I wasn't
anticipating this would be in 1.8...I figured it'd be post-1.8 unless anyone
has significant time in next few weeks (which is unlikely)
[20:18] <mdiggory> sorry, multitasking...
[20:19] <tdonohue> Ds-872 Summary: hpottinger will look at & investigate.
likely post-1.8
> Community-based feedback
> ------------------------
>
> Key: DS-872
> URL: https://jira.duraspace.org/browse/DS-872
> Project: DSpace
> Issue Type: New Feature
> Components: XMLUI
> Reporter: Eija Airio
> Attachments: patch_communityfeedback.txt, patch_conf_file.txt
>
>
> In DSpace there is only one feedback recipient. According to our experience,
> the feedback recipient often redirects e-mails of other persons, depending on
> the type of feedback.
> We developed the following feature: community-based feedback recipients,
> which are defined by inserting lines like this in the dspace.cfg file:
> feedback.recipient.123456789/2 = email1.something.com
> where 123456789/2 is the handle of the community.
> This means that when the user clicks "send feecback" in the community
> 123456789/2 (or collections, items or bitstreams under this community), the
> feedback will be sent to email1.something.com.
> If there is no corresponding line let's say for a community with the handle
> 123456789/15, the feedback will be sent to the original feedback.recipient
> email.
> There are two patches:
> patch_communityfeedback.txt, which includes small changes for
> SendFeedbackAction.java and
> patch_conf_file.txt, which include example lines in dspace.cfg
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
