Not all roles are required to catalog in Alma. However, to delete bib record, Cataloger Extended must be combined with the Cataloger role. See Managing User Roles to determine which cataloging role is appropriate for the user.
Physical Inventory Roles:
Physical Inventory roles allow a user to edit item records. Physical Inventory Operator Extended must be combined with Physical Inventory Operator for users who need to be able to delete inventory. See Managing User Roles to determine which cataloging role is appropriate for the user.
Original cataloging is done in OCLC Connexion Client/Web Client. Catalogers should create original MARC records in OCLC when a MARC record does not exist for the title/format in Alma's Network Zone and it is not in OCLC. Once a MARC record is created in OCLC, it can be exported to Alma's Network Zone.
However, if there is no MARC record in OCLC when ordering a title in Alma, a user should create a brief bib record in Alma using the SUNY brief bib record templates. This allows the library to create a brief bib record in Alma that an order record can be attached to until the title is received. Once the title is received at the library, the bib record can be cataloged in OCLC if it has not already been done by another library and updated in Alma.
Brief bib records are created for ordering when the MARC record does note exist in the Network Zone and in OCLC. The brief bib record should contain enough information to identify the record for other members of SUNY searching the Network Zone, such as the 020/022/024, 100, 245, 250, and 264. Three SUNY brief bib record templates have been created to streamline and simplify the process:
Click the following link to determine when to:
To update a brief bib that was created for ordering, the OCLC number should be added to the Network Zone bib record in MARC 035 $$a and then exported from OCLC to Alma to overlay the brief bib record with a full bib record.
Brief bib records created for ordering are the only records in the Network Zone that can be edited to add non-local MARC fields in Alma. Brief bib records are also the only Network Zone records where the MARC 035 $a (OCoLC) number can be added.
Copy cataloging is done in OCLC Connexion Client/Web Client for all MARC fields, except local MARC fields. If changes need to be made to an existing MARC record in Alma's Network Zone, catalogers should make the changes in OCLC by locking the records, editing the MARC record, replacing the record, and then exporting the record into Alma's Network Zone.
Local MARC fields are MARC fields that provide local information about the title in hand, such as gift notes or local subject headings.
Local MARC fields:
SUNY has defined local fields (called local extensions in Alma) that can be used.
Local fields (local extensions) are added in the Metadata Editor. Open the bib record in the MD Editor and go to Editing Actions>Add Local Extension (Ctrl+L). Add the SUNY appropriate local field MARC tag. A house icon will display next to the MARC tag indicating that it is a local field. Continue adding indicator/subfields and content for the local field. Save and release the bib record when done with local field changes.
If the user does not see a house display next to the field, it is not local and the user may have accidentally selected Editing Actions>Add Field. If the house icon is not next to the MARC tag, the field may be overwritten the next time the bib record is updated. The user will want to delete the field and go add the local field. Adding a local extension to a Network Zone linked record does not change the Network Zone bib record. Local notes can only be seen by the institution who created them.
Network Zone records are updated from an OCLC WorldShare Collection that is maintained by the SLS. Three files are imported into SUNY's Network instance of Alma daily at noon using an import profile. The three files are:
The following MARC field changes that trigger OCLC WorldShare records to be sent to an Update file in Alma's Network Zone are:
The following encoding levels trigger MARC records in OCLC to be sent to Alma's Network Zone:
The language of descriptive cataloging in SUNY is English, which means titles in languages other than English should be cataloged in the English language. MARC records with a language of cataloging of English can be identified by 040 $b eng. If there is not an OCLC WorldShare record with a language of cataloging of English, a parallel MARC record needs to be created in OCLC and then imported into Alma's Network Zone.
No! Changes should not be made to bib record in the Network Zone. MARC records that need to be updated must be updated in OCLC Connexion and reimported into Alma.
Adding a local MARC field (local extension) to a Network Zone linked record does not change the Network Zone bib record. Local MARC fields can be added in the MD Editor in Alma.
No! The OCLC number, as well as other non-local MARC fields, should not be edited in the Network Zone linked bib records. SUNY's Network Zone is a shared bibliographic environment and other institutions in the SUNY consortium may be linked to the same MARC records. Changing the OCLC record on a Network Zone linked record will negatively impact other SUNY institutions that are linked to the same Network Zone linked bib record.
Best practices when an institution wants to a different bib record for the title in hand:
Click the following link to view the workflows:
No! Network Zone records should only be deleted by the SUNY Library Services staff. Bib record need to be unlinked from the Network Zone prior to deleting a Network Zone linked record in the MD Editor. Bib records being deleted using a job do not need to be unlinked from the Network Zone prior to running the job.
Workflow on how to delete a Network Zone linked record in the MD Editor.
Alma has three icons to represent the zone a bib record linked to:
Not all MARC fields in the OCLC WorldShare record are in the Network Zone linked and Institution Zone only records because SUNY uses normalization rules to prevent certain MARC fields from being imported into Alma's Network and Institution Zones. Best practices also indicate that SUNY institutions should use the institution copy of the SUNY OCLC Norm Rule when importing records using import profiles.
MSP-45: Normalization Rules in the Network and Institutional Zone to see which MARC records are omitted from being imported into Alma.
Yes! Institution Zone only records (have a house icon) are not part of the SUNY shared bibliographic environment and can be edited and updated by the institution.
Users should order from, or link to, physical bibliographic records in the Network Zone (NZ) that are not linked to the Community Zone (CZ).
Most physical bib record should be linked to the Network Zone because SUNY is a Consortium using a shared bibliographic environment. Access to a large repository of bib records benefits all member in SUNY by allowing us to see which institutions hold titles and gives us the ability to share resources with one another. Linking physical bib records to the Network Zone enriches the SUNY shared bibliographic environment.
Exceptions: The following types of physical bib records should not be linked to the Network Zone:
Institutions can share Institution (IZ) only records to the Network Zone at any time as long as the records meet the criteria to be part of SUNY's shared bibliographic environment (see MSP-3 for a list of exceptions). IZ only Records can be linked to the Network Zone using the "Share with Network" function in the MD Editor or running a job on a set of records. Once an IZ only bib record is shared with the Network Zone, the record will inherit the Network Zone bib record and local bibliographic information may be lost if it has not been created as local fields.
Note: IZ only physical records should only be linked to the Network Zone. IZ only electronic resources should only be linked to the Community Zone (CZ).
Bib records are locked for up to an hour once they have been opened in the MD Editor and they have not released. Locked records will prevent other users being able to edit the bib record in the MD Editor or export a record from OCLC to Alma. It is not possible to identify the user who has locked the record in Alma, therefor it is recommended to wait for approximately and hour and then try opening the bib record in the MD Editor or exporting a record from OCLC to Alma. Best practice is to release bib records from the MD Editor after the user is done working on it.
Possible ways a bib records are locked by another user:
There are two ways to tell if a bib record has been locked by another user:
Contact SUNY Library Services if a record remains locked for over an hour: email@example.com
Most SUNY institutions publish physical bibliographic holdings automatically from Alma using a publishing profile that sends a file to their OCLC WorldShare datasync collection. All physical titles that have a set management tag of “Publish bib” are automatically published to OCLC when new physical titles are added, changes are made to existing bib records, or bib records are deleted in the Institution. Bib records are published to OCLC on a daily or weekly basis, depending on the institution’s configuration.
Institutions that subscribe to OCLC Connexion and don't use publishing profiles in Alma will need to manually publish their holdings in OCLC.
The default set management tag is “Publish bib” when new bib records are added to an institution. Import profiles can be configured to “Don’t publish” for new titles being added to the institution. Best practice: Physical titles imported into Alma as “Don’t Publish” should be changed to “Publish bib” during the receiving/cataloging processing so the holdings are accurately added to OCLC.
Contact SUNY Library Services if you are not sure if your institution is publishing bib holdings to OCLC from Alma: firstname.lastname@example.org
Bibliographic holdings changes will be published to OCLC 2-3 days after OCLC has received the file from Alma. Files are sent from Alma to OCLC either daily or once a week.
If your institution is publishing your holdings from Alma to OCLC, you do not need to manually remove holdings in OCLC if "Delete bibliographic records (unless other holdings are present)" is selected when withdrawing the last item or withdrawing items using a job. Bib records that are deleted in Alma will be sent to OCLC with LDR position 5 of "d", which tells the OCLC automated process to remove your holdings from these bib records. Holdings will not be removed in OCLC if the bib record is not deleted and remains in the institutions repository.
If your institution is not publishing your holdings from Alma to OCLC using publishing profiles, you will need to manually remove the holdings in OCLC after deleting the bib records in Alma.
No! Physical holdings should be on physical holdings in the Network Zone. Do not add your institution's holdings on e-resource titles in the Network Zone that are either linked to the Community Zone (CZ) or managed in the Network Zone for SUNY Institutions.
CZ records contain a number starting with (CKB) in 035 $a. They may also contain an OCLC number that matches the title in hand, but it should not be used. Maybe CZ records are using physical material type records erroneously.
Network Zone managed collections will either contain a (CKB) number in 035 $a or a non-OCLC number in 035 $a, such as (ODN). Please do not add your holdings to these records or edit the 035 $a field.