elifesciences / schematron-wiki

This contains the markdown from gitbook for schematron.
MIT License
2 stars 0 forks source link

Update Toggl page #142

Closed naushinthomson closed 3 years ago

naushinthomson commented 4 years ago
JGilbert-eLife commented 3 years ago

@bcollins14 @FAtherden-eLife @Melissa37 @naushinthomson The update to this page is now completed.

https://app.gitbook.com/@elifesciences/s/productionhowto/toolkit/toggl

I didn't want to overdo the information here - have I covered everything sufficiently and is everyone happy with the revised layout?

Thanks!

bcollins14 commented 3 years ago

Looks great, thanks James! đź‘Ť

Melissa37 commented 3 years ago

Could we change

to double-check the team has time to work on projects outside the day-to-day tasks

To

to monitor the team's availability to work on projects outside the day-to-day tasks

Melissa37 commented 3 years ago

To help monitor the performance of the Kriya proofing system, it is helpful to track the time taken to refresh the page and to assign articles. However, it's accepted that other tasks may be completed while the page is reloading, so these should take priority in terms of tracking.

I don't really understand what the instruction is. If Toggl cannot track two things at once, and people are favouring other task they do concurrently, the data we get from this is incomplete?

Melissa37 commented 3 years ago

Meetings Recommended description: The name/purpose of the meeting

Should meetings have a list of preset ones, to help have clean data? eg Staff meeting; huddle; update with Melissa; Exeter call, Press meeting?

Melissa37 commented 3 years ago

As a general point, as the tags have evolved there is inconsistent use of capitalisation and it bugs the copy editor in me :-)

eg all the "Emails:" are followed by a lowercase, except for "Emails: Pub date query" Projects have Continuum Checks, yet Home page.

Could we clean that up or would it mess with the data for you James?

Melissa37 commented 3 years ago

Another general comment - this looks so complicated! But I guess it is second nature to you all but I feel bad for the burden imposed just to get data :-( It will be interesting to see how Claudia manages this and whether there is feedback on that and the cost-benefit ratio needs adjustment

JGilbert-eLife commented 3 years ago

To help monitor the performance of the Kriya proofing system, it is helpful to track the time taken to refresh the page and to assign articles. However, it's accepted that other tasks may be completed while the page is reloading, so these should take priority in terms of tracking.

I don't really understand what the instruction is. If Toggl cannot track two things at once, and people are favouring other task they do concurrently, the data we get from this is incomplete?

I'd like to straw-poll the others about what they do with refreshing. @naushinthomson @bcollins14 - how have you been recording refreshing the page? Have you? Or should we just drop this?

For the meetings, @Melissa37, do we care about getting fine details of meetings? How long we huddle, for example? I'm happy to add preset options, but I'd like more guidance from the team on what those should be! :)

naushinthomson commented 3 years ago

I'd like to straw-poll the others about what they do with refreshing. @naushinthomson @bcollins14 - how have you been recording refreshing the page? Have you? Or should we just drop this?

I believe we've already covered this in a chat on huddle now :)

naushinthomson commented 3 years ago

There are descriptions of each of the email tags except for 'Emails: reproducibility' - is this still to be added?

Otherwise this looks fine to me! I've asked Claudia to have a look over it as well :D

naushinthomson commented 3 years ago

From @griffithsc :D

Very comprehensive and helpful in that it explains exactly when to use each tag/project and provides clarification on what to include in the description (which I wasn’t 100% sure on before)