Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RT2: fpage, lpage, journal from Elements to eSchol #72

Open
DevinSmithWork opened this issue Jan 22, 2025 · 1 comment
Open

RT2: fpage, lpage, journal from Elements to eSchol #72

DevinSmithWork opened this issue Jan 22, 2025 · 1 comment

Comments

@DevinSmithWork
Copy link
Collaborator

DevinSmithWork commented Jan 22, 2025

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?
@DevinSmithWork
Copy link
Collaborator Author

DevinSmithWork commented Jan 22, 2025

Scope of the problem: fpage appears quite frequently in RT2 logs:

List of grep -c from 2024-11-20 to 2025-01-18
  • connectRT2.2024.11.20:169
  • connectRT2.2024.11.21:204
  • connectRT2.2024.11.22:491
  • connectRT2.2024.11.23:496
  • connectRT2.2024.11.24:23
  • connectRT2.2024.11.25:120
  • connectRT2.2024.11.26:104
  • connectRT2.2024.11.27:41
  • connectRT2.2024.11.28:541
  • connectRT2.2024.11.29:388
  • connectRT2.2024.11.30:696
  • connectRT2.2024.12.01:304
  • connectRT2.2024.12.02:194
  • connectRT2.2024.12.03:297
  • connectRT2.2024.12.04:300
  • connectRT2.2024.12.05:575
  • connectRT2.2024.12.06:814
  • connectRT2.2024.12.07:1608
  • connectRT2.2024.12.08:142
  • connectRT2.2024.12.09:175
  • connectRT2.2024.12.10:259
  • connectRT2.2024.12.11:278
  • connectRT2.2024.12.12:620
  • connectRT2.2024.12.13:6
  • connectRT2.2024.12.14:2
  • connectRT2.2024.12.15:556
  • connectRT2.2024.12.16:1691
  • connectRT2.2024.12.17:1601
  • connectRT2.2024.12.18:715
  • connectRT2.2024.12.19:656
  • connectRT2.2024.12.20:997
  • connectRT2.2024.12.21:735
  • connectRT2.2024.12.22:560
  • connectRT2.2024.12.23:864
  • connectRT2.2024.12.24:1225
  • connectRT2.2024.12.25:1461
  • connectRT2.2024.12.26:1143
  • connectRT2.2024.12.27:730
  • connectRT2.2024.12.28:1413
  • connectRT2.2024.12.29:379
  • connectRT2.2024.12.30:48
  • connectRT2.2024.12.31:34
  • connectRT2.2025.01.01:157
  • connectRT2.2025.01.02:365
  • connectRT2.2025.01.03:624
  • connectRT2.2025.01.04:2049
  • connectRT2.2025.01.05:538
  • connectRT2.2025.01.06:343
  • connectRT2.2025.01.07:471
  • connectRT2.2025.01.08:262
  • connectRT2.2025.01.09:382
  • connectRT2.2025.01.10:845
  • connectRT2.2025.01.11:1001
  • connectRT2.2025.01.12:0
  • connectRT2.2025.01.13:439
  • connectRT2.2025.01.14:970
  • connectRT2.2025.01.15:241
  • connectRT2.2025.01.16:657
  • connectRT2.2025.01.17:585

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant