-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Members of DOAJ Team not showing up in completion reports #1379
Comments
What kind of reporting are you expecting for those users? I'm not very familiar with the prov. reporting, but if they're admins then only accepting and rejecting applications seem to be counted. Whereas if you're It picks the best role that describes you, with "admin" trumping all others. Is it possible these 2 users didn't accept/reject any applications in August? I suppose it might be helpful to have them at Tech thing: https://github.com/DOAJ/doaj/blob/develop/portality/tasks/reporting.py#L188 |
cc @richard-jones a +1 for the decision log ;) |
Yes, it would be good to remember why we made this decision about the reporting. As Emanuil says, reports for a given user are done based on their most senior role. Since both of these users are admins, only accept and reject events are reported on, regarding status changes. It should also report on "edit" events for these users though. @dommitchell - what outputs are you expecting for these users? They would only appear in the reports if they did actually do something, as the report is based on the provenance records in the system. If a user doesn't have a provenance record, they won't be in the report. As the provenance records are kept, we can always adjust the parameters/behaviours of the reporting scripts to count things differently. |
Number applications completed per month.xlsx
First off, the reports build month on month so this isn't just August. If you look at the attached, they are missing entirely. See the report sent to me, attached here. Thanks for your help! |
Ok, we figured this out! There's a bug where if you have the role "api" as your first role, it won't count anything you did. We'll get a fix in for this shortly, and can re-run all the reports retrospectively. |
Thanks to @richard-jones for the fix. I've re-run the reports using the following command on the background server:
So you should see the reports in your emails. They're also here for your convenience. |
Hello @Steven-Eardley Thanks for that! kamel Could you please check and re run? |
@Steven-Eardley
Cenyu is the report with 0 because obviously her highest role is Maned and
she did not reject or accept applications
We need to see the output of the ambassadors in the report surely
TOM
Dr. Tom Olijhoek
Editor-in-Chief DOAJ
Support us: www.doaj.org/support
…On Wed, Sep 13, 2017 at 10:44 AM, ClaraDOAJ ***@***.***> wrote:
Hello @Steven-Eardley <https://github.com/steven-eardley> Thanks for that!
The reports now show our editors, but not the ambassadors:
kamel
pascalsou
ivonne
inasmith
solomon
cenyu *this one is on the report but the numbers indicate 0 (not sure it
is correct)
xinbi *curiously this one is on the report
yanhong
sridhar
leena
vrushali
mahmoud
Could you please check and re run?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1379 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALeWRKJaONPj_iMtBpKduchZPbqu56Gzks5sh5XZgaJpZM4PSvmp>
.
|
Referring again to Emanuil's comment above, the code we use to determine whether to include something in the report is this: def _is_countable(self, prov, role):
countable = False
if role == "admin" and (prov.action == "status:accepted" or prov.action == "status:rejected"):
countable = True
elif role == "editor" and prov.action == "status:ready":
countable = True
elif role == "associate_editor" and prov.action == "status:completed":
countable = True
return countable Since we look for a user's 'best role', if a user has role editor we will only include them in the report for actions where they set an application status to Tom was right when he said that's why Cenyu shows 0 for this month, she's an admin and only has 2 rejections, back in February (which you can see on the report). I've verified this by searching the live index using the following query: {
"query": {
"filtered": {
"filter": {
"bool": {
"must": [
{"term" : {"action" : "status:ready"}}
]
}
},
"query": {
"term" : {"user": "ivonne"}
}
}
},
"sort": [{"last_updated" : "desc"}]
} and I get no results because she has not set anything to ready. If I pretend Ivonne is an associate editor, and check for So, the reports are working as originally specified. It's up to the DOAJ team whether:
If you'd like to change the reports, we can look at that under tnm. |
Additionally, Xinbi is included in the report because they have in fact been setting applications to ready, so their actions are counted under the editor role. |
@Stephen-Eardley
I understand the way the reporting works
But in my recollection all ambassadors always set apps to completed
except for Xin whom I gave the editor role specifically because I wanted
him to manage Yanhong in the Group China..
In all cases except the China editorial group where Xin is editor the Admin
takes the role of editor in the group checking the apps done by the
ambassadors and setting it to accepted or rejected bypassing ready
For instance Africa NW Alejandra editor, Africa South East Tom editor,
Russia Sonja editor.
So we need to see for the ambassadors is their output in setting things to
comleted (although they may have the possible rle of editor in the admin
system
In my view this is the origin of the problem with not seeing in the reports
what we want to see
Dr. Tom Olijhoek
Editor-in-Chief DOAJ
Support us: www.doaj.org/support
…On Wed, Sep 13, 2017 at 12:52 PM, Steven Eardley ***@***.***> wrote:
Referring again to Emanuil's comment above, the code we use to determine
whether to include something in the report is this:
def _is_countable(self, prov, role):
countable = False
if role == "admin" and (prov.action == "status:accepted" or prov.action == "status:rejected"):
countable = True
elif role == "editor" and prov.action == "status:ready":
countable = True
elif role == "associate_editor" and prov.action == "status:completed":
countable = True
return countable
Since we look for a user's 'best role', if a user has role *editor* we
will *only* include them in the report for actions where they set an
application status to ready. For the ambassadors above, I see they all
have the roles [api, editor, associate_editor] so they are considered
*editors*.
Tom was right when he said that's why Cenyu shows 0 for this month, she's
an *admin* and only has 2 rejections, back in February (which you can see
on the report).
I've verified this by searching the live index using the following query:
{
"query": {
"filtered": {
"filter": {
"bool": {
"must": [
{"term" : {"action" : "status:ready"}}
]
}
},
"query": {
"term" : {"user": "ivonne"}
}
}
},
"sort": [{"last_updated" : "desc"}]
}
and I get no results because she has not set anything to ready.
If I pretend Ivonne is an *associate editor*, and check for
status:completed, I get 373 total records. These would appear in the
report if Ivonne wasn't an *editor*, therefore having *associate_editor*
as best role.
So, the reports are working as originally specified. It's up to the DOAJ
team whether:
- Ambassadors should be *editors*, thereby only counting their *ready*
changes
- The reports *only* show your actions at your *highest role* (this
would be a TNM change)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1379 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALeWRJWNI-UOrjpjVHa-fDLtfVJ_A3fJks5sh7PsgaJpZM4PSvmp>
.
|
@Steven-Eardley
I did some more checking and indeed the ambassadors except for Xin have
never set anything Ready because they were told to set status to completed
I thought that they all had ass editor status and therefore I told Xin
that he had the editor status and could set yanhongs apps from completed
to ready
Now it seems that all have api,ass editor and editor status but they only
put apps to completed.
The Maneds acted as editors for the ambassador editorial groups and set
things to accepted or rejected by passing the Ready status
Cenyu is a separate case because she had been given the admin rights in
order to do investigations of questionable publishers
So what we need to see is the nrs of apps set to completed by the
ambassadors
In the reporting system their highest status of editor lets the system look
for ready statuses and these are 0
Dr. Tom Olijhoek
Editor-in-Chief DOAJ
Support us: www.doaj.org/support
…On Wed, Sep 13, 2017 at 2:33 PM, Tom Olijhoek ***@***.***> wrote:
@Stephen-Eardley
I understand the way the reporting works
But in my recollection all ambassadors always set apps to completed
except for Xin whom I gave the editor role specifically because I wanted
him to manage Yanhong in the Group China..
In all cases except the China editorial group where Xin is editor the
Admin takes the role of editor in the group checking the apps done by the
ambassadors and setting it to accepted or rejected bypassing ready
For instance Africa NW Alejandra editor, Africa South East Tom editor,
Russia Sonja editor.
So we need to see for the ambassadors is their output in setting things to
comleted (although they may have the possible rle of editor in the admin
system
In my view this is the origin of the problem with not seeing in the
reports what we want to see
Dr. Tom Olijhoek
Editor-in-Chief DOAJ
Support us: www.doaj.org/support
On Wed, Sep 13, 2017 at 12:52 PM, Steven Eardley ***@***.***
> wrote:
> Referring again to Emanuil's comment above, the code we use to determine
> whether to include something in the report is this:
>
> def _is_countable(self, prov, role):
> countable = False
>
> if role == "admin" and (prov.action == "status:accepted" or prov.action == "status:rejected"):
> countable = True
> elif role == "editor" and prov.action == "status:ready":
> countable = True
> elif role == "associate_editor" and prov.action == "status:completed":
> countable = True
>
> return countable
>
> Since we look for a user's 'best role', if a user has role *editor* we
> will *only* include them in the report for actions where they set an
> application status to ready. For the ambassadors above, I see they all
> have the roles [api, editor, associate_editor] so they are considered
> *editors*.
>
> Tom was right when he said that's why Cenyu shows 0 for this month, she's
> an *admin* and only has 2 rejections, back in February (which you can
> see on the report).
>
> I've verified this by searching the live index using the following query:
>
> {
> "query": {
> "filtered": {
> "filter": {
> "bool": {
> "must": [
> {"term" : {"action" : "status:ready"}}
> ]
> }
> },
> "query": {
> "term" : {"user": "ivonne"}
> }
> }
> },
> "sort": [{"last_updated" : "desc"}]
> }
>
> and I get no results because she has not set anything to ready.
>
> If I pretend Ivonne is an *associate editor*, and check for
> status:completed, I get 373 total records. These would appear in the
> report if Ivonne wasn't an *editor*, therefore having *associate_editor*
> as best role.
>
> So, the reports are working as originally specified. It's up to the DOAJ
> team whether:
>
> - Ambassadors should be *editors*, thereby only counting their *ready*
> changes
> - The reports *only* show your actions at your *highest role* (this
> would be a TNM change)
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#1379 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ALeWRJWNI-UOrjpjVHa-fDLtfVJ_A3fJks5sh7PsgaJpZM4PSvmp>
> .
>
|
Steve, what's your thoughts on this one please? |
It looks like this might just be a modification in requirements as to how we count things. We should probably just carefully re-define what the report should be showing. Right now the "completed" report shows "completion" actions, dependent on user class, and assumes that users do not have more than one class (e.g. that administrators are not associate_editors). It's easy enough to modify these rules, and we have all the data from the provenance system, so we can re-run the reports with new rules to see the new answers. Some options occur to me:
We could discuss this at our meeting tomorrow. |
Alternatively, if you remove the editor roles from the ambassadors, their completed status changes will be counted without any changes to the reports and I could just re-run them. I'd recommend modifying the reports, though - we could get a more complete picture of what is happening if we change the data collection restrictions. |
@Steven-Eardley @richard-jones thanks for your analysis.
No, we wouldn't need to at this stage.
I actually think it would be good to have both options (1) and (2) so that we get the total activity and then a breakdown, should we need it. But let's discuss this on our call today. |
'alejandra' and 'ilaria' both issing from completion by month and completion by year reports. How many others are missing??
alejandra's roles: api, admin, editor
ilaria's roles: api, admin, editor, associate_editor
Please fix and re-run August reports
The text was updated successfully, but these errors were encountered: