Articles with DOIs are easier to verify because you can click the DOI and review the published version of record.

We would like a "has DOI" and "NO DOI" facet because this would speed up Smart Harvest author matching, and potentially allow lower-level staff to review.

Staff could review "has DOI" matching and check the published version to verify affiliation. Records requiring more review or investigation could be left for higher-level staff.

Many of us work on approving an asset of a specific researcher or a specific academic unit in the 'Author matching approval task list'.

Once we choose an asset to work on, and we click on ‘Additional approval tasks exist’, there is no way to get back to the specific filtered list we were working on, and we need, again, to select the relevant filters.

We ask to add a 'Back' button.

You can look at the attachment for an example.

When approving Smart Harvest matches in the client, sometimes it is easy to tell that an asset is not a journal article, etc. For example if the title has the word Comment or Abstract as part of the title.

Right now you must approve the match and exit author matching to update asset type. This is not efficient, and I often forget to update these.

Sometimes it is impossible to confirm Smart Harvest results unless you have a current CV or publication list.

We would like to be able to send lists of unapproved Smart Harvest results to individual researchers to confirm or reject.

Initially, we would like to just send an email to researchers. Eventually, we would like them to be able to mark confirm/reject and reply and the Smart Harvest list would update.

When a researcher is incorrectly matched, we often have to create a new non-affiliated one in the record. We can add their affiliation, but we can't add research topics. If the name is common, we have to look them up by researcher and add the research topics.

It would be more efficient to add research topics (as keywords) during this step.

We've noticed that once a Smart Harvest or Smart Expansion asset is approved, there is no record of which user account approved the asset.

For training and quality control purposes, we would like to know who has approved these assets. Please consider adding this function to assets that have been sourced via Smart Harvest and Smart Expansion.

We submitted this as a bug, but have been advised it is an enhancement request.