Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Link Fixer

...

A record newly created in the MDE is immediately assigned a record ID, even though the record has not entered Princeton's repository. The ID displays in both the record header in the Main Pane and the Records list in the Left Pane. For a bib record, its MMS ID starts with 99; for a holdings record, its PID starts with 22 (See Alma System Numbers).

A new record displays the badge New in its headers. You won't be able to retrieve the record from Princeton's repository by the record ID (or any other search criteria), because the record exists in your MDE only and is visible to you alone.

...

Your editing is saved in the MDE every 30 seconds after a change is made in order to prevent data loss. Hover over icon no. 15 to see the timestamp of the last auto-save.

...

Expand
titleHas the record (or its current version) been saved into Princeton's repository?

When a record is saved to Princeton's repository, the badge New disappears from its header.

When a new bib record is first saved to Princeton's repository, a 001 field is added, displaying the MMS ID that is showing in the record header.

Another new field that is generated is 005, which stores Date and Time of Latest Transaction.

When you retrieves a WorldCat record via Search Resources and perform Copy & Merge on an existing Alma record, the merged version displays a 001 value that does not match the MMS ID of the original Alma bib being overlaid. This version has not entered Princeton's repository and has yet to be saved.

In the example on the left, WorldCat record # 2000000 is overlaying the Alma bib 99122457322006421. In the merged version, the 001 field displays the OCLC control number, but, upon Save Record, will be replaced by the MMS ID 99122457322006421.


Release records

Release Record means to release a record from your Metadata Editor when you are done with editing it. It is separate from deleting a bib/holdings record.

One of the Alma features that differ from Voyager is that multiple users cannot have the same record open for editing simultaneously. When you bring a record into the MDE, it is checked out to you. This prevents multiple users from modifying the same record at the same time and overriding each other's changes.

If you have saved your editing to Princeton's repository, other users can retrieve it by searching the repository and view a read-only version of the record. Until you release the record from the MDE or until the system force releases it X number of hours after you exit the Editor, others cannot modify it.

Note that closing (icon no. 17) a record from the Main Pane of the MDE merely minimizes the record. It remains listed in the Left Pane.

...

Release displayed records in list (Icon no. 7 in the Left Pane): Release all records in the list. The pop-up window reminds you that unsaved changes will be lost.

...

You can combine this release button with the text filter box (no. 5 in the Left Pane) to release filtered records only.

...

Previous versions

The version counter starts after the first time that a record is saved. Selecting View Related Data > View Versions opens the MD Editor in split screen mode, displaying the Versions tab in the right pane.

Version: 1 indicates that the record has had its first modification. For subsequent modifications, the version number increases.

Current version

In order to see the timestamp and the cataloger ID of the current version, hover over the icon, which is available -

  • in the MDE header bar (icon no. 16 History of the record), and
  • in the read-only Record View from repository search results

Current version information as displayed in the MDE:

Same information as displayed in the Record View:

Tip

Click on the icon to display the name associated with the PU ID. This is the person who has last touched and saved the record.


No versions

View Versions concerns only previous versions you can restore.

If no modification has been made to a record and saved to the repository, then there are no previous verisions to display - and there is nothing to restore.

The wording "no versions" can be misleading. What it really means is "no previous versions were found." What you have opened is the initial and only version of the record.

All the legacy records migrated from Voyager into Alma will display this alert until a modification has been made and saved to the repository.

...