SFX V4 – Admin Changes Lieve Rottiers

SFXAdmin KBManager KBTools Other Admin changes Agenda – SFX Admin

New Lobby Design New lobby design for easier access to frequently used modules Instead of one page – new organization in two sections – data management – day to day management of SFX – the KB manager, and frequently used modules The second section – set up and Administration – task that you do less frequently – configurations, general administration and set ups.

Direct Navigation Bar Direct Navigation bar to frequently used modules and functions within the modules – in the top part of each of the tools, there is a shortcut from one tool to the other.

SFXAdmin KBManager KBTools Other Admin changes Agenda - KBManager

General Changes in SFX V4 Version 3 Global Instance Local Instance Global Knowledge Base Global Knowledge Base Global Knowledge Base Global Knowledge Base Customer-specific data Customer-specific data Version 4 One of the big changes behind the scenes is the global –local separation. SFX 4 separation of local and global fields: global data (global KB, descriptive data) will only be held in the global instance Local instances will store customer specific data: activation status and local data (date coverage, linking parameters, local parsers) Global Instance Local Instance Global Knowledge Base Customer-specific data Customer-specific data

The Add Local Button There are little places that you can see the separation between the global-local information. New add local button – this is an example from an object portfolio window. Different from version 3, there is no way to edit the Global parser and parse param. The global information is “read only” but you can overwrite it by adding local information. Another change is that we treat the Parser and Parse param as a set. If we add local information form on of them, it is mandatory to add local information for the other to.

Overriding Global Information Global Instance Global Knowledge Base Local Instance Customer-specific data Same as version 3, all the sources are active by default. The active checkbox is grayed out, in order to deactivate a source service, you should click the add local button, and uncheck the new “active” checkbox Third screenshot – local source service – the active checkbox is not grayed out – full control for all of the fields.

Target Service List Changes Option to activate all titles together with the service for aggregator databases T.Service list – for Targets that are aggregators, When activating the Target service – a pop up [dialog box] will ask if you what to activate all the object portfolios.

Object Portfolio List Changes Title search within a title list by title and identifier “Jump to” function within title lists in case the title list consists of more than one page Function to choose how many titles to display on one page (20, 50, 100) Sorting of title lists by ID and by Title Improved display of entire titles and their display conditions such as date coverage (thresholds) on one screen – get full display with “mouse over” The navigation and searching options are improved. The results display were also improved.

Object Portfolio List Changes 3 1 2 4 (ARTICULATE – MAXIMIZE THE SIZE OF THE WINDOW FOR THIS) 5

Edit Window – Main Tab All of the Edit window were reorganized – they consist of two tabs – main and additional.

Edit Window - Additional Details Tab The additional details tab – more information, most of it new to version for. Mostly administrative.

Target Description Field Part of global KnowledgeBase

Target Aggregator Field In the Target window, there is a new field to determine if the Target is an Aggregator.

Target Service AutoActive Field If the Target is an aggregator, then in the Target service the autoactive field will be defined yes by default. It can be changed by the customer to NO. Aggregator settings mean to inherit the definition from the Target.

Additional Target Service Field Changes Site down – Is free – Crossref supported – defiened by the KB team, the customer can overwrite it by checking the checkbox.

Linking Parameter Changes - 1 U/P becomes L/P or +L/P [linking instead of user] In case that you create a local target with $$parameters included in active PARSER/PARSE_PARAM fields, you will get a new L/P button with a + sign in order to indicate that linking parameters should be defined.

Linking Parameter Changes - 2 A new Description field – populated as part of the Global KnowledgeBase New: add set of parameters for institute

Institute Changes New Display name field when adding/editing institutes. Additional fields during institute specific activation: Target display name, Target threshold Target service and object portfolio threshold

Institute Changes TARGET TABLE TARGET_SERVICE TABLE Activation status Public name (empty means inherit from local) TARGET_SERVICE TABLE AutoActive (on/off/use default) Proxy (on/off/use default) Local threshold (empty means inherit from local/global) OBJECT_PORTFOLIO TABLE LINKING_PARAMETERS TABLE Value Note: if no institute specific entry then inherit from local/global

Add Object Portfolio Institute Entry You can add Institute specific thresholds.

Search Objects New search capabilities – the search starts with one initial search entry, and a different conditions can be added to the search. New search result navigation options “Person icon” indicates on a local object that can be deleted. Indication for local objects – delete button only active for local objects Add object option

Add Objects New Function to add full set of object attributes for locally created objects, including relations, all title types, authors, all identifiers. New identifier: OCLC Control number

Edit Objects – Global Objects Edit object window for global KB objects – can add local overwrite – add a local main title, local identifier, non filling characters, and assign categories

Edit Objects – Local Objects Edit object window for local objects

KBManager Object Validation OBJECT_TYPE of the object determines which attributes can be added. ISBN, Date of publication, DOI can only be added for monographs ISSN, CODEN can only be added for serials Changing OBJECT_TYPE between serial – monograph is not possible once object has been created. SERIAL MONOGRAPH CONFERENCE JOURNAL NEWSPAPER SERIES TRANSCRIPT WIRE DATABASE BOOK CD DISSERTATION DOCUMENT MANUSCRIPT PROCEEDING REPORT

KBManager Object Validation - 2 Titles which can be added depending on language selected – esp. for CJK Validation checks against: ID duplication Multiple occurances of IDs which are not allowed Exact and partial match of authors Bi-directional relations are created automatically

KBManager - Additional Validation Parser and parse_param Thresholds Linking parameters

SFXAdmin KBManager KBTools Other Admin changes Agenda – SFX Admin

Exporting Institute Specific Coverage Export Tool Exporting Institute Specific Coverage In all TXT export files: Additional column will be added in case institutes have been defined in the instance. Column header will be ‘Institute’. This new column will contain the name of the institute (or DEFAULT) for which the row in the TXT file applies to. Advanced export – XML export

Exporting Institute Specific Coverage Export Tool Exporting Institute Specific Coverage Advanced export queries: XML export When creating export with more than one institute selected (or default and institute) AND when the same TS is active for more than one institute: In case none of the institute specific activations has an institute specific threshold statement: use only one 866 tag   </datafield>   <datafield tag="866" ind1="" ind2="">    <subfield code="a">Available from 2000. </subfield>    <subfield code="i">InstA, InstB</subfield>    <subfield code="j">InstC</subfield>    <subfield code="s">110975593244097</subfield>    <subfield code="t">110975593244095</subfield>    <subfield code="x">EBSCOhost Business Source Premier:Full Text</subfield>    <subfield code="z">110976733153888</subfield>

Exporting Institute Specific Coverage Export Tool Exporting Institute Specific Coverage in case at least one of the institute specific activations has an institute specific threshold statement: include multiple 866 tags   </datafield>   <datafield tag="866" ind1="" ind2="">    <subfield code="a">Available from 1965. Most recent 1 year(s) not available. </subfield>    <subfield code="i">InstA</subfield>    <subfield code="j">InstC</subfield>    <subfield code="s">110975593244097</subfield>    <subfield code="t">110975593244095</subfield>    <subfield code="x">EBSCOhost Business Source Premier:Full Text</subfield>    <subfield code="z">110976733153888</subfield>    <subfield code="a">Available from 2000. </subfield>    <subfield code="i">InstB</subfield>    <subfield code="z

Exporting Institute Specific Coverage Export Tool Exporting Institute Specific Coverage Advanced export queries: XML export When creating export with more than one institute selected (or default and institute) AND when the same TS is active for more than one institute: In case none of the institute specific activations has an institute specific threshold statement: use only one 866 tag   </datafield>   <datafield tag="866" ind1="" ind2="">    <subfield code="a">Available from 2000. </subfield>    <subfield code="i">InstA, InstB</subfield>    <subfield code="j">InstC</subfield>    <subfield code="s">110975593244097</subfield>    <subfield code="t">110975593244095</subfield>    <subfield code="x">EBSCOhost Business Source Premier:Full Text</subfield>    <subfield code="z">110976733153888</subfield>

Exporting Institute Specific Coverage Export Tool Exporting Institute Specific Coverage Html Export – will be kept in V4 Export tool – but institute specific thresholds will be ignored Aleph Sequential Export – export active thresholds - in case more than one institute is selected, and institute threshold is different between institutes, include 866 per threshold – but no indication of 'i' or 'j' in aleph sequential format – and no new option in this format to include institute information in the MARC records

Dataloader New option: loading institute specific thresholds New mechanism for loading title information: each title needs min. 3 required columns: - TITLE_TYPE - TITLE_VALUE - TITLE_NON_FILING For translation titles: 4th column: - TITLE_LANGUAGE

Category Tool SFX V3 SFX V4 GLOBAL_CAT GLOBAL_SUBCAT GLOBAL_CAT_SUBCAT GLOBAL_CAT_ASSIGN Note: the GLOBAL_CAT and GLOBAL_SUBCAT tables include a field to store local translations Tables used to store Ex Libris categories/subcategories and assignments: KB_CAT KB_SUBCAT KB_CAT_SUBCAT KB_CAT_ASSIGN LOCAL_CAT LOCAL_CAT_ASSIGN LOCAL_CAT_SUBCAT LOCAL_SUBCAT Tables used to store customer categories / subcategories and assignments: LCL_CAT LCL_SUBCAT LCL_CAT_SUBCAT LCL_CAT_ASSIGN LCL_TRANS_CAT LCL_TRANS_SUBCAT

A-Z index building Dependency on RSI index – for performance reasons

SFX back-up SFX will use Ex Libris Backup procedures which are used across products.

Thank you! learn@exlibrisgroup.com