Closed LucieGueuning closed 5 years ago
Per discussion on Skype:
Particularly because of 3, but also supporting user preferences around RSS feeds and display, I am wondering why an RSS feed reader application and/or bookmarks bar cannot be used alongside REACH instead, e.g. as per following screenshot. To do this task would require writing a whole new full featured RSS feeder (that can save individual preferences, do scheduled polling rather than our on-demand "hack") etc.
For reference, particularly on illustrating some of the above issues, tagging specific requests https://github.com/MSFREACH/msf-reach/issues/395 https://github.com/MSFREACH/msf-reach/issues/384 https://github.com/MSFREACH/msf-reach/issues/127 https://github.com/MSFREACH/msf-reach/issues/271
Speaking with Remi; for other regions https://github.com/MSFREACH/msf-reach/issues/455 sounds like we do need to replicate /embed some RSS reader features within REACH at some point. So need to think about workload around database, UI and API changes on that front. And need to promote use of georss. https://github.com/MSFREACH/msf-reach/issues/417
@anexact need your UX feedback on how we do this
Embedding RSS (incl non-geospatial) within the system (database and UX) could allow AI to leverage this information alongside everything else.
@mehrdadgit I've made a start on this in https://github.com/MSFREACH/msf-reach/commit/16e7a525ac6e69c6b23e34dc2fd69bec1c0a6d0d and corresponding schema change https://github.com/MSFREACH/msf-reach-schema/commit/6bbe1e1cedabed82d449abb3f1fe4532f568dd11 Todo:
@matthewberryman I do not understand what is the markdown field for ? Is this the name/title of RSS feed ? if so, why does it have to be in markdown format ? Also if bookmarks table is going to store the custom RSS Feeds for the user, should we store the feed URL somewhere, in the same (or separate) table ?
Requirements for RSS feed: On landing page:
On event page:
Does that make sense?
@LucieGueuning
Just to be clear, we are doing first two items to satisfy 2b requirements, the rest is 2c extension work.
@mehrdadgit The markdown field is for the full markdown text that specifies the full list of bookmarks (titles and urls), e.g.
* [MSF REACH](https://msf-reach.org)
* [My company web site](https://acrossthecloud.net)
* [My mechanical computer](https://brunsviga.io)
which renders as:
@matthewberryman
Ok well noted.
points 1 and 2 for Phase 2b point 3 for Phase 2 extension point 4 (event page): cover by Qiao and Paul UX/UI revamp package
should be ready for testing @matthewberryman
@LucieGueuning ready for testing in the test environment (test.msf-reach.org) with starting default links per https://github.com/MSFREACH/msf-reach/issues/416 (note there seemed some overlap with ENSO links so I only added one to save a bit of space but can add others back in).
FEEDBACK:
Synchronised map and table for RSS feed geo-enable
Separate issues, see #668 and #669
ability to customised the same way the geo-enable one. SOL: Having a second balck button next to the first one with: 'Open geospatial news feeds'. And then possibility to remove, add or edit the link for geo-enable. It then sends a request to add it manually to the map or can it be automatic? How can we have the customised RSS feed for geo spatial ones?
There are a number of design & new / existing features requested in this item^^
Can we have an arrow to return back to edition, more user friendly. You don't want to close that window, you just want to go back to the previous one.
@mehrdadgit can add that button to go back from help to editing.
bug in the edit pop-up display:
This is not a bug but a way that the formatting language works. If you add any spacing between the [text] and the (link) then it shows them separately (with the long link overflowing). I've added some additional help text, in 89c4f0fcf5258b734a4c1a572e6589a5ab25735b , to clarify.
For the last comment: I know, imagine if the hyperlink is to keep and that long, it will be out of the box.
Gotcha @luciegueuning I will fix that.
Go back button and long-hyperlink-bug fixed; note it is on #174 branch.
Thanks Mehrdad. This can go to prod, to be confirmed with Matthew
Great, I will move to prod tomorrow (my time) - just a bit busy this afternoon and I need to make sure I get the database changes in correctly for this one.
@mehrdadgit I'll also need to go through and cherry-pick your latest commit over to the issues/453 branch to merge just that (while work proceeds on issues/174 branch).
Important feature to keep as such on GitHub. No duplication