User & Service Updates Technical Questions

[wesleyboar]

Context

Create User & Service Updates for new TUP CMS site. (#95)

Questions

User & Service Updates

1. Where does the data come from?
2. Are there any changes desired in how it is managed?
3. Any known gotchas in data retrieval or display?
4. Do the subscription and news publish automatically occur together?
5. How are service updates and user news distinguished on the data side?
6. (New) What does the data look like?
7. (New) Is Portal filtering/cleaning the data?
8. (New) Are there any documentation or gotchas for the API calls to retrieve updates?
9. (New) May I have either access to the BitBucket repo or the specs from it?

Subscription (to Updates)

1. What software manages the subscription?
2. Does the switch to MailJet affect this feature?
3. Who manages the subscription lists?
4. Do the subscription and news publish automatically occur together?
5. (New) Are there any documentation or gotchas for the API calls to edit subscription?

Reference

Steps for User to Subscribe

1. User submits email.
2. User gets e-mail with link to manage subscription.
3. User may manage subscription via link from e-mail.
   • Some items user is subscribed to at first.
   • Some items user is not subscribed to at first.

Status

W.B. should ask J.Y.—or look for the code—about filtering data from TAS:

User & Service Updates

6. What does the data look like?
7. Is Portal filtering/cleaning the data?

[wesleyboar]

Answers (from T.C.)

User & Service Updates

1. TAS. How does it get on front page? Unclear, check with J.Y. or A.R.
2. Yes, but they are outside the scope of CMS.
   • Creation of entires is archaic.
   • Unable to test (even though there is a button).
   • Based on TAS.
3. Ask J.Y. or A.R. LSS and A.S.*
4. Yes.
5. Via same tags as the Systems. Confirm with J.Y. or A.R. LSS and A.S.*

* reason for change

Subscription (to Updates)

1. TAS
2. No.
3. T.C.
4. Yes.

[wesleyboar]

Notes

(Far) Future

• TAS is being rebuilt as TRAM.
• T.C. considers this feature need not be in TAS2/TRAM.
• No timeline for TRAM.

Reference

• Technical: J.Y., A.R., A.S.
• Administrator: H.P.

[wesleyboar]

Answers (from A.S.)

User & Service Updates

5. The service updates and user news are distinguished by however we want to interpret the tags. Notice, an entry with the "Site/Services" tag could also have a "Frontera" tag, or could have no other tags.
6. (New) What does the data look like?
   • Ask J.Y.
7. (New) Is Portal filtering/cleaning the data?
   • Ask J.Y.
8. (New) Are there any documentation or gotchas for the API calls to retrieve updates?
   • Yes, for API, see Bitbucket repo (pending access), or specs copied from it
9. (New) May I have either access to the BitBucket repo or the specs from it?
   • Yes (repo). Alternatively, see taccus.tas-swagger-ui.spec.json.txt.

Subscription (to Updates)

3. Admins & Users.
   • Admins: The admin console manages lists.
   • Users: A user is auto-subscribed when they sign up for a system but can also unsubscribe (after receiving link in e-mail).
4. There are options
   • "Save": Publish update and Send to mailing list.
   • "Save & Send": Publish update but do not Send to mailing list.
5. No. The subscription is not available via API. It is a standalone web app, but API access could be added.
   • To get API support, create TAS JIRA ticket—or if you cannot—then create RT ticket. Akhil Seth says he can do it.
   • Without API, you must use existing standalone web app (iframe it in like portal, whether on its own page, a box in a page, or in a modal).

[wesleyboar]

Status

Paused. WMA wants more involvement in discussion of a solution.

[wesleyboar]

Investigation Transferred

FP-1056: Investigate TUP User News on New TACC CMS