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
Copy file name to clipboardExpand all lines: README.md
+55-2
Original file line number
Diff line number
Diff line change
@@ -277,10 +277,63 @@ Run Python from the virtual environment (see Python Virtual Environment document
277
277
278
278
Where `--dso_type`is`[communities|collections|items|people|bitstreams]`
279
279
280
+
## Jupiter Delta Report
280
281
281
-
## Jupiter Delta
282
+
### Jupiter Delta Report: Overview
283
+
284
+
Given that notallERA content can be frozen, a delta report aims to communicate any changes to the ERA content from a specified date until the time the report is run. The report aims to communicate each content change leveraging the same data enabling ERA/Jupiter versions UI. Each change event is recorded as a row in a Google Sheet contain both the changed Jupiter fieldname/value data and the Scholaris mappings for the fieldname/value data.
285
+
286
+
The assumption is the number of actionable changes is small and a human can leverage the information in the report to
287
+
288
+
* see that a Jupiter object has changed
289
+
* identify the Scholaris fieldnames to update and the Scholaris value
290
+
291
+
### Delta Report: How to use
292
+
293
+
The report can be presented and shared as a Google Doc to allow users to sort, search, modify as needed.
294
+
295
+
An early example <https://docs.google.com/spreadsheets/d/1GWxwEtM0EOyoPP5RUrf1oQCtIVz1re-8n0Be4Kybt8E/edit?gid=0#gid=0>
* change_id: change event id (PaperTrail::Version ID)
307
+
* jupiter_id: ERAID
308
+
* is_jupiter_currently_readonly: "true"if the ERAobjectis currently read only
309
+
* read_only_event: "true"if this change event only updated the read only field and the obj updated at timestamp
310
+
* changed_at: change event timestamp
311
+
* event: the type of the change record: update|destroy
312
+
* jupiter delta: jupiter change event details (what field plus old=> new values)
313
+
* jupiter delta formatted: an easier to read version
314
+
* scholaris mapper: the jupiter delta mapped to Scholaris fieldname and new value equivalents
315
+
* scholaris mapper formatted: an easier to read version
316
+
317
+
Process thoughts:
318
+
319
+
* In ERA, changing an object to "read only" creates a new version change event: the read_only_event column that indicated if change event only updates read only status thus allow one to filter/order these events if too numerous
320
+
* Sort by item_id & date ascending: this allows grouping a sequence of updates over time; if the same field changed multiple times then use the most recent.
321
+
* Event "destroy" means the object has been deleted and there will be no Scholaris mapping
322
+
323
+
Question:
324
+
325
+
* How best to present such that given a Jupiter on can easily find the Scholaris equivalent.
326
+
327
+
### Delta Report: How to generate
328
+
329
+
See script details: `jupiter_output_scripts/jupiter_delta.rb`
330
+
331
+
Rough outline:
332
+
333
+
* Needs the Ruby Class used in step 1 of SAF package generation
0 commit comments