Every Monday a report is sent out from Scholarsphere listing the previous week's uploads. Example given below.
Scan through it and ...
1) Pick out any data for curation. In the future assign to a curator. I typically put these up on this repo as an issue. Refer to #162
2) Look through other resource types for obvious errors and/or look at them on scholarsphere and ensure the information is correct.
3) If any of the problems appear to be related to the ScholarSphere make a ticket, often written as a user story (if UI related) or just as a description of the problem if it is not UI.
4) I will sometimes look through the other stats too at this point. Google analytics mainly.
Every Monday a report is sent out from Scholarsphere listing the previous week's uploads. Example given below.
Scan through it and ...
1) Pick out any data for curation. In the future assign to a curator. I typically put these up on this repo as an issue. Refer to #162
2) Look through other resource types for obvious errors and/or look at them on scholarsphere and ensure the information is correct.
3) If any of the problems appear to be related to the ScholarSphere make a ticket, often written as a user story (if UI related) or just as a description of the problem if it is not UI.
4) I will sometimes look through the other stats too at this point. Google analytics mainly.