#496 Record Monitoring Option(s) for Users

[John-Mark Gilhousen]

The "recently changed" block is helping, but I know
some of my users are missing new information on
individuals within their area of research interest,
and sending notes to people when an individual record
I know they are researching has been updated is
getting laborious.

I would like to see a feature on individual record
pages so that logged-in users could choose to be
notified if that particular record is changed, much
like the monitor feature here on Sourceview.

Or, it could be combined with the user's favorites
list on their MyGedView page as a checkbox to the add
favorite form.

An additional option in the user's account to opt in
for notifications of changes to all records within a
specified number of generations to onesself would be
gravy (or groovy, depending on how old you were in
the Sixties).

Thanks.

J-M +

[John-Mark Gilhousen]

Logged In: YES
user_id=1065899

Ok, this having landed like a lead baloon -- no comment in
the two months since I poste it -- how about at least
adding the Recent Changes block to the RSS subscribable
items?

[John-Mark Gilhousen]

Logged In: YES
user_id=1065899

Ok, this having landed like a lead baloon -- no comment in
the two months since I poste it -- how about at least
adding the Recent Changes block to the RSS subscribable
items?

[John-Mark Gilhousen]

Logged In: YES
user_id=1065899

Ok, this having landed like a lead baloon -- no comment in
the two months since I poste it -- how about at least
adding the Recent Changes block to the RSS subscribable
items?

[KosherJava]

Logged In: YES
user_id=634811

Don't assume that a lack of comment for 2 months is a bad
sign. In this project developers pick RFEs that interest
them and implement it. We are all volunteers, and we don't
just assign tasks to developers. There are many RFEs that
are very old, and a developer will just pick up on a whim
and implement. Having an RFE allows us to track it and not
forget it. So keep the faith in the system!!
The Recent Changes is part of the RSS feed for 4.0 and will
not likely be back ported to 3.3.x.

[John-Mark Gilhousen]

Logged In: YES
user_id=1065899

1. My apologies for accidentally spamming here with
multiple entries. Apparently my browser or the
sourceforge server hiccoughed, and I was not aware of it
until the duplicates landed in my e-mail inbox.

2. Because I'm using Jommla on my site, I am sticking
with 3.3.x until 4.0 has a stable release, and the Joomla
component can be modified to it. I am installing the beta
versions as they are released on the various systems I
have available, just to check for any otherwise unreported
bugs I can spot, but am not making those installations
public. So, I am not as fluent in the features and
changes in 4.0 as perhaps I should be. Too many threads
on here to read 'em all. I do wish there was a way to
easily port this fix back to 3.8, since it is unclear how
long 4.0 will be in beta, and even longer for a Joomla
update for it.

3. I understand non-response should not be
considered "bad" in the sense you mean it. I just thought
making the request simpler might give me a better shot at
getting a tool I could use. You would not believe the
number of "did you notice that new information on so-and-
so has been posted" e-mails I send out in the course of
each and every week.

[John-Mark Gilhousen]

Logged In: YES
user_id=1065899

1. My apologies for accidentally spamming here with
multiple entries. Apparently my browser or the
sourceforge server hiccoughed, and I was not aware of it
until the duplicates landed in my e-mail inbox.

2. Because I'm using Jommla on my site, I am sticking
with 3.3.x until 4.0 has a stable release, and the Joomla
component can be modified to it. I am installing the beta
versions as they are released on the various systems I
have available, just to check for any otherwise unreported
bugs I can spot, but am not making those installations
public. So, I am not as fluent in the features and
changes in 4.0 as perhaps I should be. Too many threads
on here to read 'em all. I do wish there was a way to
easily port this fix back to 3.8, since it is unclear how
long 4.0 will be in beta, and even longer for a Joomla
update for it.

3. I understand non-response should not be
considered "bad" in the sense you mean it. I just thought
making the request simpler might give me a better shot at
getting a tool I could use. You would not believe the
number of "did you notice that new information on so-and-
so has been posted" e-mails I send out in the course of
each and every week.

[John-Mark Gilhousen]

Logged In: YES
user_id=1065899

1. My apologies for accidentally spamming here with
multiple entries. Apparently my browser or the
sourceforge server hiccoughed, and I was not aware of it
until the duplicates landed in my e-mail inbox.

2. Because I'm using Jommla on my site, I am sticking
with 3.3.x until 4.0 has a stable release, and the Joomla
component can be modified to it. I am installing the beta
versions as they are released on the various systems I
have available, just to check for any otherwise unreported
bugs I can spot, but am not making those installations
public. So, I am not as fluent in the features and
changes in 4.0 as perhaps I should be. Too many threads
on here to read 'em all. I do wish there was a way to
easily port this fix back to 3.8, since it is unclear how
long 4.0 will be in beta, and even longer for a Joomla
update for it.

3. I understand non-response should not be
considered "bad" in the sense you mean it. I just thought
making the request simpler might give me a better shot at
getting a tool I could use. You would not believe the
number of "did you notice that new information on so-and-
so has been posted" e-mails I send out in the course of
each and every week.