CUNY Graduate Center - Project Tracking System: Issueshttps://redmine.gc.cuny.edu/https://redmine.gc.cuny.edu/favicon.ico2024-03-19T15:39:55ZCUNY Graduate Center - Project Tracking System
Redmine CUNY Academic Commons - Feature #20014 (New): Reskin of Group Libraryhttps://redmine.gc.cuny.edu/issues/200142024-03-19T15:39:55ZBoone Gorgesboone@gorg.es
<p>See Figma file linked at <a class="external" href="https://redmine.gc.cuny.edu/issues/19592#note-14">https://redmine.gc.cuny.edu/issues/19592#note-14</a></p> CUNY Academic Commons - Feature #20013 (New): Support for Commons-provided cover images in group ...https://redmine.gc.cuny.edu/issues/200132024-03-19T15:34:39ZBoone Gorgesboone@gorg.es
<p>See <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Updating Group/Site Creation and Completion pages (New)" href="https://redmine.gc.cuny.edu/issues/19724">#19724</a>. This ticket is a placeholder for now, but once the 2.4.0 branch is set up so that cover image support is unlocked during group creation/editing, I'll ask Jeremy to begin taking a look at how we can integrate his work from the CV creation flow into the group creation/editing flow.</p> CUNY Academic Commons - Feature #19980 (Assigned): Better duplicate-notification prevention for b...https://redmine.gc.cuny.edu/issues/199802024-03-14T15:49:10ZBoone Gorgesboone@gorg.es
<p>bp-multiple-forum-post was written before BPGES started using an asynchronous queue technique for sending notifications. As a result, its mechanism for preventing duplicate notifications - which involves a runtime global - is not effective. Instead, we should prevent BPGES from entering a record into the queue table when we see that the user already has the activity item in his/her queue.</p>
<p>This in itself will not be enough. If you post to A and cross-post to B, you could have a situation where:<br />1. The item is queued with respect to group A, and bp-multiple-forum-post schedules a task to create the crossposts<br />2. BPGES runs its "immediate" queue and your A notification goes out. It's then deleted from the queue.<br />3. Later, bp-multiple-forum-post creates its crossposts. Since the A notification has been cleared from the queue, the check described above won't be found.</p>
<p>Modifying BPGES to keep a persistent queue seems like a bad idea - it'd mean introducing a 'status' column, and it'd mean keeping items around forever, unless we had a cleanup routine.</p>
<p>I guess the alternative is to keep track in some other way of users who have received notifications (or, better still, users for whom a BPGES notification has been queued) on a cross-posted item. There's no beautiful way to do this. I guess maybe a piece of postmeta that lives with the original post, which will have to be checked when bp-multiple-forum-post creates the crossposts.</p> CUNY Academic Commons - Feature #18194 (New): Migration routine for CVshttps://redmine.gc.cuny.edu/issues/181942023-05-09T17:38:21ZBoone Gorgesboone@gorg.es
<p>When we introduce the new CV feature <a class="issue tracker-2 status-5 priority-4 priority-default closed child" title="Feature: CV Editing and Publishing (Resolved)" href="https://redmine.gc.cuny.edu/issues/17768">#17768</a> we will need to migrate over existing user data. Some initial thoughts for discussion:</p>
<p>- We should not create CVs for all existing users. How do we decide? I propose that we should only create them for users who have at least one "bottom" section filled in - Education, Positions, Publications, etc. Does anyone else have suggestions for how this should work?<br />- We'll have to build block markup using a pipeline like <code>serialize_blocks()</code>. This is likely to be subject to all sorts of issues with character encoding, etc, so we'll have to find some outlier profiles to use for testing. Ones with lots of fields built in, etc.<br />- Should old data - ie the BP profile data - be deleted or kept? It depends in part on whether we will continue to use the BP profile data. I'm thinking in part of directory search. If we do this, we'll need a mechanism in the regular CV save routine that syncs the relevant fields to BP's profile data system.</p>
<p>The migrator will have to be one of the last things built, since it'll depend on the specifics of the CV block implementation. See <a class="issue tracker-2 status-5 priority-4 priority-default closed parent" title="Feature: CV "top" section (Resolved)" href="https://redmine.gc.cuny.edu/issues/18192">#18192</a>, <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: CV "bottom" section (Resolved)" href="https://redmine.gc.cuny.edu/issues/18193">#18193</a>.</p> CUNY Academic Commons - Design/UX #17677 (New): Cataloguing notification typeshttps://redmine.gc.cuny.edu/issues/176772023-02-16T18:54:32ZBoone Gorgesboone@gorg.es
<p>Following up on a recent dev call, here's a list of unique notification types on the Commons:</p>
<pre>
| added_reader |
| bbp_new_reply |
| comment_mention |
| followedpaper_comment |
| followedpaper_edit |
| friendship_accepted |
| friendship_request |
| group_invite |
| membership_request_accepted |
| membership_request_rejected |
| member_promoted_to_admin |
| member_promoted_to_mod |
| mypaper_comment |
| new_at_mention |
| new_membership_request |
| new_message |
| new_wire_post |
| pending_booking |
</pre>
<p>We can eliminate several that are related to Social Paper: <code>added_reader</code>, <code>comment_mention</code>, <code>followedpaper_comment</code>, <code>followedpaper_edit</code>, <code>mypaper_comment</code>. In addition, <code>new_wire_post</code> is linked to a feature that we no longer have on the Commons. This leaves us with:</p>
<p>1. bbp_new_reply - Created by bbPress for user A when user B posts a reply to a forum topic or reply written by A. <br />2. friendship_accepted - Created by BP for user A when user B accepts a friendship request that A sent to B.<br />3. friendship_request - Created by BP for user A when user B sends a friendship request to A.<br />4. group_invite - Created by BP for user A when user B invites A to join a group.<br />5. membership_request_accepted - Created by BP for user A when A requests membership in a group, and the group's admin approves the request<br />6. membership_request_rejected - Created by BP for user A when A requests membership in a group, and the group's admin rejects the request<br />7. member_promoted_to_admin - Created by BP for user A when A is promoted in a group from 'member' to 'admin'<br />8. member_promoted_to_mod - Created by BP for user A when A is promoted in a group from 'member' to 'mod'<br />9. new_at_mention - Created by BP for user A when A is at-mentioned anywhere tracked by BuddyPress. Notably for our purpose, this includes blog posts, blog comments, forum posts.<br />10. new_membership_request - Created by BP for user A when A is the admin of a private group, and user B requests membership in that group<br />11. new_message - Created by BP for user A when A receives a private message<br />12. pending_booking - Created by the events-manager plugin for user A when user A has created an event with booking, and user B books for that event. events-manager is <strong>not</strong> a plugin that we run on the main site, so this must be something that happens on secondary sites</p>
<p>Of these, a number are purely informational. 1, 2, 5, 6, 7, 8, 9, 12 A right-hand notifications pane could have a message that summarizes the information ("So-and-so replied to your forum post") and then links to that content.</p>
<p>Several of them have obvious follow-up actions. 3, 4, 10, perhaps 11. A right-hand notifications pane could have a link that points you to the page where you'd perform the action, or perhaps it could show you the interface for actually performing the action (ie, accepting the friendship).</p>
<p>I hope this is a helpful start.</p> CUNY Academic Commons - Support #11883 (New): Need Embedding Help Page Update (Tableau)https://redmine.gc.cuny.edu/issues/118832019-09-19T21:43:37ZAnthony Wheeler
<p>Hi Scott,</p>
<p>So I was recently trying to embed a Tableau visualization into a Commons site when I ran into a couple of roadblocks. I went to our Help Page for embedding from other websites, and it was helpful, but something we may want to add is that when copying the share link over from Tableau, you have to make sure you copy the link under "Original View" <br /><img src="https://redmine.gc.cuny.edu/attachments/download/12443/Screen%20Shot%202019-09-19%20at%205.40.11%20PM.png" alt="" /></p>
<p>It was only after that discovery that the visualization was fully functioning within the Commons. I attached (or tried to attach) a screenshot to hopefully show you what I'm talking about.</p>
<p>Thanks!</p> NYCDH Community Site - Feature #10631 (New): DATA VIS - Flyer and Cardshttps://redmine.gc.cuny.edu/issues/106312018-10-29T18:19:49ZAlex IrklievskiAIrklievski@gc.cuny.eduNYCDH Community Site - Feature #10630 (New): Digital Humanities - Flyer and Cardshttps://redmine.gc.cuny.edu/issues/106302018-10-29T18:14:33ZAlex IrklievskiAIrklievski@gc.cuny.eduNYCDH Community Site - Feature #10628 (New): Data Science - Flier and Cardshttps://redmine.gc.cuny.edu/issues/106282018-10-29T18:07:24ZAlex IrklievskiAIrklievski@gc.cuny.eduNYCDH Community Site - Feature #10627 (New): Compu Linguistics - Flyer and Cardshttps://redmine.gc.cuny.edu/issues/106272018-10-29T18:01:39ZAlex IrklievskiAIrklievski@gc.cuny.eduNYCDH Community Site - Feature #10626 (Assigned): Cognitive Neuroscience - Flyer and Cardshttps://redmine.gc.cuny.edu/issues/106262018-10-29T17:52:37ZAlex IrklievskiAIrklievski@gc.cuny.eduNYCDH Community Site - Feature #10625 (New): IMS - Flyer and Cardshttps://redmine.gc.cuny.edu/issues/106252018-10-29T17:44:21ZAlex IrklievskiAIrklievski@gc.cuny.eduNYCDH Community Site - Feature #10624 (New): QMSS - Flyer and Cardshttps://redmine.gc.cuny.edu/issues/106242018-10-29T17:36:33ZAlex IrklievskiAIrklievski@gc.cuny.eduCUNY Academic Commons - Design/UX #10580 (New): Primary nav item reviewhttps://redmine.gc.cuny.edu/issues/105802018-10-24T16:29:02ZBoone Gorgesboone@gorg.es
<p>This is primarily about the main nav under the Commons logo throughout the main site, but probably also affects the "CUNY Academic Commons" dropdown at the upper-left of the toolbar.</p>
<p>Let's gather some analytic data about the use of these nav items, and think about how and whether to restructure the IA, or represent them differently (especially on mobile?).</p>
<p>Previously: <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Remove 1 item from main nav bar when we add courses (Resolved)" href="https://redmine.gc.cuny.edu/issues/10229">#10229</a>.</p> CUNY Academic Commons - Bug #4388 (Assigned): Repeated request for authentication.https://redmine.gc.cuny.edu/issues/43882015-08-05T19:43:46ZAlice.Lynn McMichaelalimcmichael@hotmail.com
<p>Hi, I'm building a site on the Commons, and when I click on a page or refresh one, a pop-up asking for authentication interrupts the work, often making me click OK up to 8-10 times. (It doesn't go away if I click Cancel, either). I can't tell whether this is Commons-wide or related to my account or theme, although it did not happen when I used a different Commons site yesterday</p>
<p>My site is not public yet, but the URL is amcmichael.commons.gc.cuny.edu and the theme is Make. I've had this problem repeatedly over the last couple of weeks. (See the attached screenshot for the pop-up box that I get).</p>
<p>Thank you.<br />Best,<br />Alice Lynn</p>