Closed fabiodrg closed 2 years ago
The issue #69 is related. Might be useful to create a Person
parser. It should support parsing from the document
or from a custom context (e.g. URL, html, DOMParser). That parser could be used in both issues (this one and #69)
One more issue to handle. looks like Sigarra server responses are encoded as text/html; charset=iso-8859-15
. As the response body is interpreted as utf-8
, weird stuff appears...
With respect to ignoring hyperlinks associated to the logged in user.. I thought it would be easy, but it looks like the hyperlinks used to access my profile near the login form and on the top bar use yet another ID is not the user ID (student up
I could fetch that URL to gather the actual user ID, just not sure if it is worth it.
Found a third type of page for users in thesis lists: https://sigarra.up.pt/feup/pt/inst_geral.ver?P_CODIGO=1891
My main motivation for this is when having to contact more than one teacher from search results or from course unit pages. The typical approach is to open the profile in separate pages and copy the links. With batch email I could select multiple users without that manual process. Furthermore, for single recipients, I could click one button near the user name/link without having to move to a different page to get the email.
Tasks
https://sigarra.up.pt/feup/en/func_geral.formview?p_codigo=<id>
. Another possible hyperlink ishttps://sigarra.up.pt/feup/pt/vld_entidades_geral.entidade_pagina?pct_codigo=<id>
. It is commonly used for students, but I have seen it for FEUP staff as well, which then redirects tofunc_geral.formview
. For example, thesis lists.mailto
hyperlinks near the original hyperlink tag, i.e.<a>