You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the prod migration, while monitoring the RT2 output and comparing against the resulting eScholarship metadata, I noticed that the updates for fpage, lpage, journal, and few others didn't seem to be registering in eScholarship.
Will differences in these fields between the two systems result in a metadata update from the Relevance scheme? If so, this may result in a TDB amount of unnecessary churn in the diff sync.
Are there differences between how eScholarship native journals and "external journals" store this data? If so, do we have a way to either:
Store the data in the appropriate metadata fields (if the fields are indeed different)? Or,
Use the transform to return two different field sets back to Elements, ergo preventing an update?
The text was updated successfully, but these errors were encountered:
During the prod migration, while monitoring the RT2 output and comparing against the resulting eScholarship metadata, I noticed that the updates for
fpage
,lpage
,journal
, and few others didn't seem to be registering in eScholarship.The text was updated successfully, but these errors were encountered: