paulalbert1

This occurs at least ~0.03% of the time, probably more as unlikely records are discarded. See query: ``` SELECT * from ( SELECT a.pmid, a1.personIdentifier, userAssertion, GROUP_CONCAT(distinct authorLastName SEPARATOR ',...

## Background The existing manner of lookups only searches by author name – not by collaborator name. Author name searches (both lenient and strict) are like this `Grinspan Z [au]`....

See issue #524

## Background There are a number of cases where a user will have org units in their profile and they don't even come close to matching the org unit on...

Update the way ReCiter handles books

1

## Scope Approximately 0.1% of records in PubMed are for books although this has increased in the past year. ## Data model Books have a different data model. Key differences...

This was encountered recently with skl9004. App should skip over alternateNames or primaryNames that lack a first name (or last name).

[These values ](https://github.com/wcmc-its/ReCiter/blob/632f53aebecc23b7d3877bca7e8b47f0f3b067b1/src/main/resources/application.properties#L45-L50)should be stored in environmental variable. This is for security reasons. It's not especially compelling, but it did appear in an audit.

Update computation of accuracy so it's consistent with best practices

2

Right now, accuracy is calculated as the average of precision and recall. We should change it to: (true positive + true negative) / (true positive + true negative + false...

The ReCiter Connect logs display the below errors. Why are we trying to run jobs for people when they don't exist? ``` 2023-04-03 10:19:39.654 INFO 1 --- [ main] reciter.Application...