I found the problem. It was bug DS-2164
<https://jira.duraspace.org/browse/DS-2164>.
I am not sure why this was not applied when I upgraded. I simply ran the
following code, and it fixed the issue.
insert into metadatavalue (
resource_id,
resource_type_id,
metadata_field_id,
text_value,
text_lang,
place)
select
eperson_id as resource_id,
7 as resource_type_id,
(select
metadata_field_id
from metadatafieldregistry
where
metadata_schema_id = (select
metadata_schema_id
from metadataschemaregistry
where
short_id = 'eperson') and element = 'email' and qualifier is null) as
metadata_field_id,
email as text_value,
null as text_lang,
0 as place
from eperson
where
not email is null;
On Thursday, September 14, 2017 at 3:57:08 PM UTC-4, Tom Avino wrote:
>
> When I query an item, the item seems to display properly. However, when I
> look in the log file I see this error. I am also having issues with
> e-persons throwing errors.
>
> ERROR org.dspace.content.DSpaceObject @ Loading item - cannot find
> metadata field -1 for resourceType=3 and resourceId=29..30..
> I get like 30 of these in the log
>
> Any help would be appreciated.
>
> Tom
>
> --
>
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
