Faculty have noticed items with due dates over two months away being flagged as being due soon in the daily digest emails. This is obviously not "soon", so I was curious about how the notification system defines "soon".
Hi Stephanie, are these notifications showing up only in digest emails, or also the activity stream?
Also, are the faculty seeing in the digest all items with due dates that far out or only some? E.g., if there are 10 items with due dates 2 months out, are all 10 showing or only a few?
I haven't heard anything about them on the Activity Stream. The first faculty who mentioned it only had 1 due date as being due "soon" in the daily digest, and that was the final exam in two months. He has due dates between now and then that were not on the digest, but I don't know if they were enabled in his course when he asked about it.
I think what I noticed the most in trying to research the problem was that the documentation on Notifications and the Activity Stream and the page on Notification settings are a little thin given how important these two communication tools are. The Activity Stream says that "Upcoming" covers events in the next seven days, but there aren't more details about "Upcoming" Notifications in the emails, so I assumed they would have been the same.
As another example, I know that I have seen notifications on the Activity Stream about students who have not been active in my courses. I have wanted to share that with faculty, but the limited information on the Notifications Settings page doesn't provide enough information. This is a cool feature - has anyone else developed information on it for faculty?
Hi Stephanie, I agree that the documentation is thin. I'll make some recommendations to our Help.Blackboard team and I'll be sure to include your feedback here. I chatted with a few engineers about this topic today and they had a host of questions for me that I could not answer. It might be best to submit a support case so that this can be thoroughly investigated. Some of the questions included things such as were items appearing in the digest as due soon recently added/edited, and if edited, in what ways; are the due soon items also noted in the activity stream and are they incorrect as per timing, etc. The engineer also asked for a copy of the email digest. If you can include this information in your case it will be most helpful.
If many of us have related questions, is it better for them to receive support cases from each of us? Also, does it matter that ours is only on our "Test" environment and not on the "production" server?
Hi Liz, yes, separate support cases are best if something is not functioning as you’d expect. If you have functional questions I’m happy to do all I can to help. You are welcome to submit cases in test and production.
It's just related to this same situation. I imported a course that is a fall (Current) course with current due dates (Thursday) but not showing in "due soon" and I feel that it should.
A support case will be helpful. Thank you, Liz!
Thanks, Misty. I don't know if we will be able to pull together a support case on this at this time, but we will try to do so.
I am still concerned that some of the details you mentioned don't seem to be relevant to an item being listed as "Due Soon". To faculty and students, "Due Soon" literally means the due date on the assessment is approaching soon - where "soon" would ordinarily be somewhere between the next day and a week or two out. Having added or edited the item recently should make it appear as new content, assuming that it is visible to students, but that isn't related to whether the due date is approaching.
I understand your concerns, Stephanie. As I was speaking with engineers about this, these were the questions they were asking me. I believe they were trying to discern if an action such as adding or editing recently was somehow flagging something as due soon. I have not been successful so far in determining thresholds for an item showing up as "due soon." I do agree with your assessment regarding what timeframe "due soon" might be. I regret having to ask you to do a support case on this, but I expect this issue will need to be escalated to teams who are better able to troubleshoot and can look into documentation regarding how these thresholds are set and how to resolve this issue.
Retrieving data ...