010 editor review Activators Patch

010 editor review Activators Patch

010 editor review Activators Patch

CRISPR activation (CRISPRa) uses dCas9 with transcriptional activators Base editing efficiency is lower in post-mitotic cells (~10%). After Microsoft releases a new update that fixes the problem, the rollback is no longer Edit your GPO to use the KIR activation policy. SweetScape Editor Crack is a powerful and easy-to-use encoder to simplify it by making code files easy to edit. The application is a text and.

Remarkable: 010 editor review Activators Patch

010 editor review Activators Patch
INFIX PDF EDITOR PRO REGISTRATION CODE
NetBalancer 10.2.5.2715 Crack + Activation Code Full Download {2021}
TOTAL AV ANTIVIRUS SERIAL KEY
010 editor review Activators Patch

010 editor review Activators Patch -

Introduction

Conditions allow you to determine where and/or when an OGL item is available/shown to the user in the application. These are called guide activation conditionsand are managed at the guide level. There also exist step conditions, these are set at the step/tooltip level within a guide.

This article focuses on guide activation conditions.

How to access the Guide Activation Settings Interface

From the OGL Console, select the check icon check icon for the guide that you want to access.
check icon location in tile

The below-pictured interface will be presented:
guide activation UI

1 = Guide Name: This shows the name of the guide

2 = These buttons are used to add new simple, advanced, and time conditions.

3 = A summary of the guide conditions

4 = Auto-Generated tag, this identifies conditions that have been automatically generated.

5 = The status of the is displayed. Active means the condition is set and active. Inactive means the condition is set but not active

6 = Edit condition button

simple condition icon = Simple Condition identifier

advanced condition icon = Advanced Condition identifier

time icon = Time Condition identifier

Note: Guide Activation conditions are evaluated using the AND Boolean operator. A guide will display/autoload if all the active conditions (C1, C2,Cn) are evaluated to TRUE. In the example above, the guide will be available in the widget only if all three conditions (simple condition icon, advanced condition icon) are evaluated to TRUE. The OR operator (denoted by the pipe character "

Managing Electronic Resources

  1. Last updated
  2. Save as PDF

Translatable

To manage electronic resources, you must have the following roles:
  • Electronic Inventory Operator
  • Electronic Inventory Operator Extended (required for delete operations)
  • Repository Manager

You create and maintain electronic collections and standalone portfolios using various editors and processes.

For an introduction to Electronic Resources, watch Electronic Resources in Alma - The Three Zones (6 min.) 

See Electronic Resources – Scenarios and Workflows to guide you in determining which workflow to follow when creating or acquiring electronic resources.

Managing Electronic Collections

Electronic collections organize electronic resources for delivery and publication. Resources can include electronic journals, portfolios, databases, or e-books, among others. They can be accessed through a service such as full-text, using bibliographic records and URLs, or by a combination of these.

Electronic collections are available (to be published to Primo or to be viewed in Primo VE) after they are activated. The exception to this is database type electronic collections. They are active if there is both a level URL at the Collection Editor - Additional tab level and also if there is an unsuppressed bib record for the collection.

You can define portfolios as standalone entities or as part of an electronic collection. The procedure for adding electronic collections and their associated portfolios is provided in Adding a Local Electronic Collection. The procedure for adding a portfolio independent of adding an electronic collection is provided in Managing Local Portfolios.

Adding a Local Electronic Collection

For a demonstration on creating an electronic collection, see the Add an Electronic Collection video ( mins).

You create and activate local electronic collections from Community Zone records if your resources exist in the Community Zone, or directly from vendor resources, if you obtain your resources from a publisher or publisher aggregator or agent. For more information specific to database type electronic collections, see Working with Database Type Electronic Collections.

Adding an electronic collection includes adding services, which describe the access to the collection's portfolios. Database collection types do not include portfolios and do not require services.

To add a local electronic collection:

  1. On the Electronic Collection Editor page (Resources > Add Local Electronic Collection), enter the basic collection information.
    Electronic_Collection_Editor_Page_NewUI_PNG
OptionDescription
Public nameThe name to display in the discovery search results.

For local electronic collections, this name can be modified later (after the electronic collection has been saved) from the Electronic Collection Description tab using the Electronic Collection Editor.

Public name (override)The name to display in place of the public name for this electronic collection.
DescriptionThe description to display in the search results (not editable).
Internal descriptionA description for internal reference only.
Collection typeOne of the following:
  • Selective Package – An electronic collection for which the library typically will activate specific portfolios (and not the entire collection).  Note that "Selective" package and "Aggregator" package behave the same when the flag "Automatically activate new portfolios" is checked in the electronic collection activation wizard.
  • Aggregator Package – An electronic collection for which the library typically will activate the entire collection (and not only specific portfolios).  Note that "Selective" package and "Aggregator" package behave the same when the flag "Automatically activate new portfolios" is checked in the electronic collection activation wizard.
  • Database – Your collection begins with an online database record.
Service Type
  • Full Text  – Display the full text of the e-resource,
  • Selected Full Text – The provider displays full text for some of the articles of the journal, but not for all of them.
  • None – Used only for databases without titles, such as abstracting or indexing databases. If you choose None, portfolios cannot be added.
LibrarySelect the library for the collection. Users can work only with electronic resources whose library is the same as the library set on their role scope. Users are prevented from performing editing/managing operations on electronic inventory of other libraries. This is to ensure that portfolio activation and other actions are only done by authorized users.

Inheritance principles and derived behavior for the library defined on the electronic resource:

ConditionResult
No library is defined on the electronic collection 
  • The electronic collection's library level is considered institution-level (across all libraries of the institution). This has the following implications:
    • All the collection's portfolios are considered institution-level.
    • Only users with institution-level role scope can manage the electronic collection and its portfolios.
  • The collection's portfolios can be set with any library. In this case, only users with institution-level role scope and the specific library scope can edit the portfolio.

Specific library is defined on the electronic collection

Defining the library on the collection deletes the library previously set on the portfolios of the collection, and portfolios now inherit the library from the collection. This has the following implications: 

  • Only users with the specific library role scope can manage the electronic collection and its portfolios.
  • Once you set a library on the electronic collection, the ability to define a library is disabled for the collection's portfolios.  
  • The "Library" parameter becomes hidden in the following locations:
    • The Electronic Portfolio search results - the portfolio-level library label is hidden, and instead the parameter "Electronic collection library" is displayed.
    • The Electronic Portfolio Editor - the portfolio-level library label is hidden, and instead the parameter "Electronic collection library" is displayed.
    • The Portfolio table list in the Service editor.
  • The library set on the electronic collection is displayed on the Portfolio Editor as a read-only parameter "Electronic collection library".

Selecting a library on an electronic collection deletes the library on all its portfolios. The deleted libraries cannot be restored. For this reason, when you add a library to a collection, a popup message is displayed: "Setting a library to the electronic collection will delete any existing library value from all its portfolios, and they will inherit the collection's library definition. This action will be done by a background process and cannot be reversed." Confirm this message to proceed. Alma displays a success message with the job ID and a link to the Monitor Jobs page where you can track the job. 

Changing the library of the electronic collection does not trigger publishing of a portfolio.

The entire inheritance flow only works if limiting E-inventory actions is enabled.
The temp_user_scope_limits_electronic_resources  customer parameter must be enabled for this functionality to work.
This parameter can only be enabled by Ex Libris Support.

  1. Select Save and Continue.
    • If you selected service type None, the Electronic Collection Editor page appears. Continue with step
    • If you selected service type Full Text or Selected Full Text, the Activation tab on the Electronic Service Editor page appears:
      Electronic service editor - activation www.buddysplantplus.com
  2. Enter the activation information.
    FieldDescription
    Service activation statusSelect Available if you want the service to be active, or Not Available otherwise.

    This field is ignored if either or both of the Active from date / Active until date fields are set.

    Activate new portfolios associated with service automatically?

    Select to automatically activate new portfolios when they are added to this service. This option is available for aggregator and selective packages.

    This option only applies to portfolios with service type Full Text. Portfolios of service type Selected Full Text do not automatically activate even if this option is set to Yes. Selected Full Text portfolios needs to be activated manually. 

    After changing this setting to Yes, new portfolios are automatically activated, but no change is made to any existing portfolios. Portfolios that were inactive prior to this change remain inactive.

    When you use this option, the resulting automatically-activated portfolios can be retrieved by using the Portfolio added to auto-active package report type in the Community Zone Updates Task List (Resources > Manage Inventory > Community Zone Updates Task List). See Portfolio added to auto-active package for more information.

    Active from dateA start date for the activation. If no start date is entered, activation starts from the current date (today).

    The activation from and until date fields override the Service activation status field.

    Active until dateAn end date. If no end date is entered, activation continues indefinitely.
    Service temporarily unavailable message

    Select Yes or No to generate a service temporarily unavailable message either on the current date or on a specific date (see Service unavailable as of date). Note that this does not deactivate the service.

    This message is generated for all associated portfolios.

    Service unavailable message as of dateA date for when the service temporarily unavailable message is generated. If not entered, the current date (today) is used.
    Service unavailability reasonThe reason to appear in the service temporarily unavailable message.

    Use the OpenURL Link Resolver to preview on the Electronic Services page what will appear in the discovery interface for patrons.

  3. Select the Service Description tab and review or edit the information as described in the table below:
    Electronic service editor - service description www.buddysplantplus.com
    FieldDescription
    Service TypeThis field has no functional implication.

    See the Initial Collection table.

    Public descriptionSee the Initial Collection table.
    Internal descriptionSee the Initial Collection table.
    Public description (override)This field is not currently functional.
  4. Select the Linking tab and review or edit the information as described in the Linking Tab Options table below.
    Electronic service editor - linking www.buddysplantplus.com
    OptionDescription
    General Linking Information
    ParserThe destination service. (Example: AIP::SCITATION)

    If the target URL of each portfolio is exactly the value of the jkey = statement in the portfolio parser parameters, use a Bulk::BULK Parser.

    Parser (override)

    A parser to override the value in the Parser field.

    Parser parametersThe linking/access information for the service. For example:

    url1=www.buddysplantplus.com? & url2=www.buddysplantplus.com & url3=www.buddysplantplus.com & agg=sfx

    Parser parameters (override)

    An override to the Parser parameters if an alternative one is specified by the service.
     

    To remove the override and restore this field for multiple records in batch, in the Portfolio Loader replace the value of this field with the value “NULL”. For details, see Restore Community Zone linking parameters (remove override of parser).

    URL TypeThe type of URL that is used for this service:
    • Dynamic URL – Select a linking URL dynamically at the service level based on the list of conditions defined in the Dynamic URL field.
    • Parser Parameters – An override for the parser’s parameters in the Parser parameters (override) field.
    URL Type (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
    Dynamic URLA list of IF conditions to determine the service’s linking URL when you select Dynamic URL as the URL Type. Select Test dynamic URL syntax to verify the syntax of the IF statements.

    For information on dynamic URLs, see Configuring Dynamic URLs for Electronic Collections and Portfolios.

    Linking levelThe linking level or unit to which the electronic collection will link such as volume, issue, or article.
    This field is for information only, it does not have any implications in Alma.
    Linking level (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here if you want to change the linking level value in your local copy. 
    Service is free?Whether or not the service is free.
    Is free (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
    Crossref supportedThis field displays whether or not CrossRef is supported in the Community Zone's electronic service for this resource. See www.buddysplantplus.com for more information regarding the CrossRef DOI (Digital Object Identifier) service.

    For records linked to the Community Zone, this field is set by Ex Libris in the Community Zone.

    For local electronic collections, you may select Yes/No. This setting is optional for local electronic collections. When you select Yes, confirm that the parser program that you select supports adding in the DOI to the URL. If it does not, setting this to Yes serves no purpose.

    Crossref supported (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
    Crossref enabledSelect Yes, No, or Inherit to indicate your preference for using the CrossRef service.
    • Yes – Get the DOI and use it for linking. You must also have your CrossRef information configured properly. See Alma Resolver Augmentation for information about configuring an Alma integration profile for DOI.
    • No – Do not use the functionality related to CrossRef for linking this electronic resource.
    • Inherit – Use the policy as defined by the previous (upper) level in the hierarchy. For a portfolio, the electronic service level policy is used. For an electronic service, the policy defined in Community Zone electronic service (as indicated in the Crossref supported field, above).
    Proxy enabledWhether a proxy is enabled

    See Resolver Proxies for information about proxy relationships among portfolios, electronic collections, and services.

    Proxy selectedA proxy profile. When you specify Yes for Proxy enabled, identify which proxy profile is used for authentication (of users outside the library’s network) to access the online database you have created. If you specify Yes for Proxy enabled and you make no selection here, Alma automatically uses the default proxy you configured.

    The procedure To configure a resolver proxy definition type of integration profile: in the Resolver Proxies section describes how to configure a default proxy profile.

    Availability rules

    Select the Service display condition rules link to view the rules automatically created by the system.

    See Display Condition Rules for more information.

    Link Resolver Plugin
    Link Resolver PluginA link resolver plugin, if needed.
    Linking Parser Parameters
    Linking Parser ParametersThe values, if needed, for the parameters configured in the parser parameter fields on the Linking tab. See the table below for more information.

    For the $$U_SHIBBOLETH parameter, the relevant entity ID must be specified. In addition, the value Yes must be entered for $$SHIBBOLETH.

    Some electronic collections require parameters that are specific to your library. For SFX customers, this information is migrated from SFX. For non-SFX customers, you must enter the values for the electronic collections to which you subscribe.

    See the following table for a description of which parameters require information for which electronic collections. Note that this table is not exhaustive. Additional electronic collections that are not listed in this table may require information for their parameters. For more information, see the SFX Target and Alma E-Collection Configuration Guide and, in particular, the Introducing E-Collection Configuration for Alma chapter of this guide for its usage with Alma.

    CollectionParametersExplanation
    ABC CLIO DatabasesUSERNAME
    PASSWORD
    An ABC representative can provide you with your user name and password.
    CCC (Copyright Clearance Center) serviceBILL, ID, INST, MAIL, and SOURCEA CCC representative can provide you with the details for each of the following linking parameters:
    • BILL – The email address used for billing.
    • MAIL – The email address used for sending an article.
    • SOURCE – The university system code, which is provided by CCC.
    • INST – The campus name code (for example, Fullerton), which is provided by CCC.
    • ID – The libraryUserID of EZProxy users, which is provided by CCC.

      If the university system and the institute are the same, the Get It Now service expects the SOURCE and INST parameters to have the same value.

    Testing access to CCC Get It Now services (using the test access action in the staff search results) will not lead the staff user to an article because the electronic resource from which test access is performed is at the journal level.

    Ebook Central Perpetual and DDA TitlesCUST_IDLibrary’s code assigned by Ebook Central. 
    EBSCO CUST_ID, OPID
    • If you add the $$CUST_ID linking parameter, your institution will automatically log in when trying to access articles and journals in the EBSCO platform.
    • If your institution adds your unique linking parameter called $$OPID in addition to the $$CUST_ID, the journal level link will work as above, but the article level links will be generated in the following way (EBSCO's new linking method): www.buddysplantplus.com{OPID}/openurl?prompt=true&{OpenURLcontextObject} 
      This is the recommended method. 

    If you only use the $$OPID parameter without the $$CUST_ID, the article level link will be created as above and will work as expected, but the journal level link will lead to the EBSCO login page. 

    • For SSO authentication - enter the value 'yes' in the SSO linking parameters
    • For SHIBBOLETH/ATHENS authentication - enter the value 'yes' in the SHIBBOLETH linking parameters
    • For IP authentication - enter the value 'yes' in the IPAUTH linking parameters

    For details, see Transition to EBSCOhost New Target Parser - December  

    EurekaCUSTOMER_IDA Eureka representative can provide you with your customer ID.
    FactivaNAMESPACE, PASS, USER
    Or:
    SID
    A Factiva representative can provide your namespace, user, and password information.
    Or:
    Specify your XSID value.

    When linking to Factiva with your XSID, there is no need to provide the other parameters.

    See the SFX Target and Alma E-Collection Configuration Guide for additional parameter details.

    All Gale DatabasesLOC_ID
    ART
    DATABASE
    A Gale representative can provide you with your institution’s LOC_ID.

    The ART parameter must be yes.

    The DATABASE parameter is only relevant for the following collections:

    • Galegroup IT Custom Journals
    • Galegroup IT Custom Newspapers
    • Galegroup Military Intelligence
    • Galegroup Religion Philosophy Collection
    Journals at OvidUSERNAME
    PASSWORD
    Libraries can connect to Ovid Journals using IP authentication or login credentials. If your library uses a user name and password, provide these values.
    IPAUTHIf your institution is authenticated by IP authorization, type yes (in lowercase letters) in the Value column. In this case, there is no need to provide a user name and password.
     For other Ovid parameter information, see the SFX Target and Alma E-Collection Configuration Guide.
    CSA DatabasesUSERNAMEProvide your library’s user name and access values.
    ACCESS
    ProQuest DatabasesCLIENTID

    A Client ID is necessary for users in a collaborative network implementing a Network Zone. In other cases, the Client ID is not necessary for linking to ProQuest databases, but may enable additional services, depending on your institution’s license with ProQuest.

    Some ProQuest databases ask for CLIENTID, while others for ACCOUNTID. This is the same value in both cases, the ProQuest account ID.

    A ProQuest representative can provide you with your Client ID.

    For the Chadwyck electronic collections based on the ProQuest platform, refer to the SFX Target and Alma E-Collection Configuration Guide for parameter details.

    WestlawSPONSORCODEA Westlaw representative can provide you with your customer code.
  5. Select the Portfolios tab:
    Electronic service editor - portfolioi www.buddysplantplus.com
    From the Portfolios tab, you can perform the following actions:
    ActionDescription

    Add Local Portfolio

    To add a local portfolio to the service, select Add and select Add Local Portfolio. The New Portfolio page appears. See Adding a Standalone Portfolio and the New Portfolio Page Options table for more information. 

    When you have completed the information on the New Portfolio page, select Save and Done. Alma saves the portfolio and refreshes the Portfolios tab of the Electronic Service Editor page with options for activating (and deactivating) the portfolio.

    You can add the portfolio information later by doing one of the following:

    Load PortfoliosSelect an Excel-formatted file to load multiple portfolios. For more information, see Adding, Editing, or Removing Portfolio Information in Bulk
    Add from setAdd portfolios from an existing set. Select to open available sets, then select one. Note that this is not an option for collections that are linked to the Community Zone.

    After adding at least one portfolio, the following additional actions are available

    These actions are enabled only if the library set in the electronic resource matches the library defined on the user's role scope. For other electronic resources, these actions are disabled. For details, see Library set on electronic resource. 

    Actions (for each portfolio)Select the following operations for a portfolio:
    • Edit – Open the Electronic Portfolio Editor in edit mode. For more information, see Editing a Portfolio Using the Electronic Portfolio Editor.
    • View – Open the Electronic Portfolio Editor in view-only mode.
    • Test Access – Display the portfolio on the Electronic Services page (or when selecting Display in a new window, if direct linking is enabled).

    When a Vendor website does not support iframe, Test Access displays a blank screen. For such cases, use the Display in new window option.

    • Remove – Delete the portfolio. In the confirmation dialog box, select whether to:
      • Delete the bibliographic record
      • Do nothing
      • Suppress the bibliographic record
    • Deactivate – Deactivate the portfolio.
    • Duplicate – Duplicates the local portfolio information (internal description, PO line, override information such as coverage, authentication note, and public note) from the local portfolio from which you selected this action, and opens the Electronic Portfolio Editor page with the duplicated information for you to edit.
    Activate SelectedActivate the selected portfolios
    Deactivate SelectedDeactivate the selected portfolios
    Deactivate AllDeactivate all portfolios in the list
    Activate AllActivate all portfolios in the list
    Delete SelectedDelete the selected portfolios. In the confirmation dialog box, select whether to:
    • Delete the bibliographic records
    • Do nothing
    • Suppress the bibliographic records
    Tools   Tools_Icon_Extended_Export_and_Excel_png
    • Extended Export – Export the list of portfolios with extended information to Excel
    • Excel (Current View) – Export only the fields appearing in the list of portfolios to Excel

    The export can include inactive (Not Available) portfolios.

    For more information, see Portfolio Loader.

    Specific to exporting portfolios from Alma to BrowZine, see Exporting Electronic Portfolios from Alma to BrowZine in the Developers Network.

  6. In the Notes tab, you can enter an authentication note (a note related to authentication (to display in the discovery system) and a public note (information about the service (to display in the discovery system). For more information, see Notes Tab.

    When a group setting is defined for an Electronic Collection, a public note defined in the Electronic Service Editor does not trickle down to portfolios. If a group setting is defined, define the public note in the Notes tab of the Collection Editor or in the service-level Group Settings Profile.

  7. You can view information about changes to the service on the History tab (for more information, see History Tab). There is no information on this page when the service is first created. Each change includes the following information:

    • Date
    • Operator – The user who made the change.
    • Field Name – The field that was changed. All fields of the Electronic Collection are tracked for changes. 
    • Old Value
    • New Value
  8. To restrict access to the resource(s) based on location, select the Group Settings tab and enter the necessary information. You must first configure inventory management groups (see Configuring Distributed Access to Electronic Resources). 

  • Electronic Collection Editor > Group Setting Tab

     Should only be used for Alma Electronic Collections and Databases not indexed in CDI.&#;&#;&#;&#;&#;&#;

  • Electronic Collection Editor > CDI > Group Setting Tab

     Should be used to only assign group settings to Databases indexed in CDI.

 

  1. Select Add Settings for Group. The Available For Information dialog box appears.

  2. Select the group to which to restrict the resource.
  3. For Proxy Enabled, select:
    • Yes – Add a proxy when resolving this resource. Specify the proxy in the Electronic Collection Proxy selected.
    • No – Do not add a proxy when resolving this resource.
    • Resource Default – Use the proxy definition from the resource. See Resolver Proxies for information on the hierarchy of proxy relationships among portfolios, electronic collections, and services. The default resource is determined by this hierarchy.

      If using a proxy for resources limited to a specific inventory management group, set this option to 'Yes'. Setting it to 'Resource Default' for a group might not resolve correctly.

  4. Add a public name for the resource, and authentication or public notes, as required.

    For public notes limited to a specific inventory management group, always include the campus/library that belongs to this group in the openUrl.

  5. Select Save Settings

For an example, see Configuring Distributed Access to Electronic Resources.

  • Select Save to save all the entries and changes on the Electronic Service Editor page. The Electronic Collection Editor page appears.
    access model on portfolio www.buddysplantplus.com

    Electronic Collection Editor

    • Review the tabs on the Electronic Collection Editor page and confirm your settings. See the table below for an explanation of the Electronic Collection Editor page tabs and fields.
      OptionDescription
      Collection NameThe electronic collection name.
      Collection IDThe electronic collection ID.
      Electronic Collection Description tab:

      See the Initial Collection table.

      General tab – Summary and Inventory Information section:

      (Most of this information is relevant only for Database type electronic collections.)

      Electronic collection typeSelect a different electronic collection type if you decide to follow a more service-oriented ordering model.
      Type (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
      Interface nameThe vendor interface for this database.

      A link to the vendor interface description is provided when an interface name is entered.

      Interface name (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
      ServicesThe services information, if it is available.

      Process type

      The only value that this field can display is 'Acquisition'. It is populated automatically once you click the Order row action on a Community Zone collection. This indicates that this collection was activated as part of the Acquisition workflow. 

      In other cases this field is blank. 

      Access type

      Access type can be specified by one of the following options that identifies the licensing rights for the electronic collection:

      • Current – This is the default option. For the electronic collection that you are creating, this identifies the licensing arrangement for which you are currently subscribing, paying.
      • Perpetual – For the electronic collection that you are creating, this indicates that the titles of the collection have permanent access during the period of a license agreement.
      • Current and perpetual – For the electronic collection that you are creating, this identifies the licensing arrangement that includes both current and perpetual resources.

      Access type data is also available in Analytics.

      See Electronic collection access type and Access type (Portfolio) for more information.

      Access type (Electronic Collection)

      COUNTER Platform

      Use this parameter to indicate the platform by which you want usage data tracked for a specific electronic collection for Alma Analytics usage data and cost-per-use reports.

      The list of options for this parameter comes from the list of platforms included in the loaded COUNTER reports. In order to have values appear in this list, you must have loaded COUNTER reports.

      Note that if you leave the COUNTER Platform parameter blank, there is no change in the way that the usage data is tracked for Analytics reporting. That is, no platform-specific data is tracked for the electronic collection.

      General tab – Acquisitions and License Information section:

      (Most of this information is relevant only for Database type electronic collections.)

      PO line

      The main PO line created for the database type electronic collection being added.

      When trying to link an electronic collection to a PO Line, the PO Line must be of type Electronic Collection (Onetime or Subscription).

      When adding a database type electronic collection, you may skip this option and process the order information later, after saving the database inventory record.

      PO line detailsA link to the main PO line details, if available.
      Public access model

      Displays the active access model associated with the portfolio, as inherited from the PO line that created the portfolio. Any updates to the access model on the PO line are reflected in this field. You can also change the value of this field, and this determines the active access model of the portfolio. However, changing the access model on the portfolio does not update the access model on the PO line. 

      • In case a PO line of type 'License Upgrade' was added to the portfolio as an additional PO line, the Public Access Model field on the portfolio displays the access model associated with the license-upgrade order.
      • There is an option of disabling the presentation of the access model in the Discovery system via Configuration menu > Fulfillment  > Discovery Interface Display Logic > Other settings. This will disable presentation of the access model in the Discovery system for all electronic resources.

      To control the presentation of the access model to patrons via Alma Link Resolver, institutions now can use a designated configuration located under Fulfillment > Discovery Interface Display Logic > Other settings. Select the checkbox Enable Display of Access Model to display in Primo the access model information located on the portfolio. The Enable Display of Access Model option is disabled by default. Institutions that want to control the presentation of the access model to patrons via Alma Link Resolver, need to select the Enable Display of Access Model option. See Configuring Other Settings.

      Activation dateThe date on which the resource was marked as activated. Note that this is not necessarily the same as Activation from date (defined in the Activation tab).
      Expected activation dateThe expected activation date.
      LicenseThe vendor license for the collection that you are adding.
      View license detailsA link to the license details when an active license is selected.

      Additional PO Line

      A list of any additional PO lines associated with this collection. Select a link to view information about the PO line. To associate other PO lines as additional PO lines for this collection, search for or enter the PO line number in the Quick Add section and select Add PO Line. To remove a PO line as an additional PO line, select Delete in the additional PO line's row.
      General tab – Historical License Information section:

      This section appears only if a license was defined. Lines are added to this section each time the license changes. Select View to open the License Details page for this license.

      Additional tab – Electronic Collection Information section:
      SourceFor future use.
      Source IDFor future use.
      CreatorFor future use.
      Alternative titleFor future use.
      Electronic Collection Level URL

      This is the URL entered for the local electronic collection. Up to 1, characters (longer URLs are trimmed).

      For a Community Zone record, this may be the URL identified in the Community Zone for the (activated) electronic collection. See Working with Electronic Collection Bibliographic Records and URLs Added to the Community Zone for more information.

      For a database type of electronic collection, this field and the Additional descriptive information are required for the electronic collection to be active and published to Primo.

      Both this field and the Additional descriptive information must be specified for the Institution Zone icon to become active.

      Electronic Collection Level URL (override)This is the URL entered to override the URL provided in the Electronic Collection Level URL field entered for the local electronic collection. See Working with Electronic Collection Bibliographic Records and URLs Added to the Community Zone for more information.
      Electronic Collection is free?Whether the collection is free.
      Is free (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
      Electronic Collection Proxy EnableWhether to enable a proxy.
      Electronic Collection Proxy SelectedA proxy profile. When you specify Yes for Electronic Collection Proxy Enable, identify which proxy profile is to be used for authentication (of users outside the library’s network) to access the online collection. If you specify Yes for Proxy enabled and you make no selection here, Alma automatically uses the default proxy.

      See Resolver Proxies for information regarding how to create a proxy profile. The procedure To configure a resolver proxy definition type of integration profile: in the Resolver Proxies section describes how to configure a default proxy profile.

      LanguageThe language of the collection.
      Language (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
      CategoryThe subject that the online collection handles (optional). This field has no functional use.
      Category (override)Appears only for collections linked to the Community Zone. If you are the collection contributor, enter a value here to update the collection in the CZ. If you are not the contributor, enter a value here to update your local copy. 
      Additional descriptive informationThe MARC bibliographic record to link to this collection.

      The MARC bibliographic record selected for this option appears in the discovery (Primo) search results. This is the MARC bibliographic record that the library’s cataloger has created specifically for the collection being added. This field is required for publishing to Primo.

      This field and Electronic Collection Level URL are required for the database to be active and published to Primo.

      Both this field and Electronic Collection Level URL must be specified for the Institution Zone icon to become active.

      Number of portfolios

      The number of portfolios in the portfolios list. Select this link to open the Porfolios List page connected to the electronic collection.

      Character setThe character set information.
      Additional tab – Services section:
      Add Local ServiceAdd a service to the electronic collection that you have open. See Adding a Local Electronic Collection, starting with the bullet under step 2 that references the Electronic Service Editor page for more information regarding adding a service.
      RefreshUse this function to follow the progress of a background job that is deleting services. When you select Refresh, the service information that appears in the Services section is updated.
      Refresh_in_the_Services_Section_of_the_Electronic_Collection_Editor_06_www.buddysplantplus.com

      Refresh

      Service rows

      The following actions are available for each service row:

      • Edit
      • View
      • Portfolio List - This opens the Portfolios tab on the Electronic Service Editor page.
      • Deactivate
      • Delete

        This initiates a batch process to delete the service. You are prompted with a Delete confirmation message where you can select how to handle bibliographic records with no inventory when your delete request is processed. Your options are Do nothing, Delete bibliographic record(s), or Suppress bibliographic record(s).

        Select Confirm to process your delete request, and check the History tab on the Monitor Jobs page (see Viewing Completed Jobs) to view the results of your job. A job submitted confirmation message appears.

        See Delete Electronic Service Job Report on the Viewing Completed Jobs page for more information.

      Notes tab: For more information, see Notes Tab.

      Authentication noteA note related to authentication (to display in the discovery system).
      Public noteInformation about the database (to display in the discovery system).
      Group Settings tab – See the Group Settings tab explanation above in the step for editing the Group Settings tab. Also see Configuring Distributed Access to Electronic Resources.
       The following changes in this dialog box apply for services:
      • A service does not have a public name
      • Enter any required linking parameter values. These parameters are defined on the Linking tab of the service. The values are used by the OpenURL link resolver to create correct links. For detailed information, see the Library-Specific Parameters table above and the SFX Target and Alma E-Collection Configuration Guide including the Introducing E-Collection Configuration for Alma chapter of this guide for its usage with Alma.
      History tab – Information on this tab is only relevant when editing the electronic collection.
       

      This is a read-only tab that displays a list of changes that were made to the electronic collection or the electronic collection's group settings (for institutions where the multi_campus_inventory_management customer parameter set to true).

      Select one of the following radio buttons to indicate the historical information that you want to view:

      • Portfolio changes
      • Group Settings changes

      For each change that is saved, the following information appears on the History tab.

      Only changes made in the UI or by internal system processes appear in this tab; changes made by any other job do not.

      • Date of the change
      • Operator that made the change
      • Group Name   
      • Name of the field that was changed
      • Old (previous) value
      • New value
      For fields/columns that are blank or empty, a dash appears in the History tab columns.

      For more information about this History tab, see the History Tab for Electronic Resources video ( mins).

      CDI tab – Except for the Do not share as Full Text available in CDI even if active in Alma field, all other fields on this tab appear only when the collection is indexed in CDI (i.e. the Available for CDI search activation facet is set to Yes).

      Alma_CDI_Tab_CDI_www.buddysplantplus.com

      CDI Tab - Collection Indexed in CDI

      CDI Search activation status (only available when the CDI model is Fully Flexible)

      This setting controls which records will appear in the Primo ‘Expand’ search (when user selects the Expand beyond the Library collection option).

      When set to Active, records from the collection will appear in the Discovery expand search. Records will be flagged as No full text available, unless there are full text activations for this collection. For the full text activations, the indication ‘Full text available’ will be shown.

      When set to Not Active, records from the collection do not appear in the search results at all.

      • Alma collections that you have active, because you subscribe to their full text, will become automatically searchable in CDI. For those collections no separate search activations are necessary.
      • Collections that require a subscription to be searchable (for example, A&I databases) need to be active in Alma to be searchable. Such collections are marked on Alma as Search Rights in CDI: Subscription. Such collections cannot be simply activated for search because of the way the activation is published to CDI. If you subscribe to such collection, you need to activate it in Alma (in the same way you activate a full text collection) or set the collection to Full text in CDI only: Yes to ensure this collection will become searchable in CDI. Note that the word “full text” in “Full text in CDI only” is a bit misleading in the context of A&I databases but this function can still be used for such collections (see details in the “Active for full text in CDI only" section).

      CDI-only full text activation

      This option is used when the library does not want to publish the bibliographic records of the collection and its content to Primo or to use the collection in the link resolver. It can be used for all collections that use Link in record type of linking in CDI, regardless of whether the collection has portfolios or not. Content of collections that are using Link in record type of linking in CDI are set to full text available on the collection level. If Do not show as Full Text available in CDI even if active in Alma is selected as well, an error is generated when saving.

      If you create groups in the CDI Group Settings section, the CDI-only full text activation appears only in the individual groups and is hidden from the institution section.

      The effect of using this option is:

      • The collections and the portfolio bib records are suppressed in Alma and are not published to CDI.
      • The collection level record is published to CDI in the zero title file with the effect that the collection is set to full text available and is discoverable in CDI.

      We subscribe to only some titles in this collection

      Select Yes to indicate a selective subscription (where you subscribe to only part of the content) or No to indicate a non-selective subscription for this collection (where you subscribe to all of the content in the collection).

      This option is available only for Aggregator/Selective collections (not for Database types of collections where no portfolios exist). The default setting is Yes.

      Selecting No should be done only in case your subscription is non-selective (for example for aggregator collections or where you subscribe to the full content of the collection) and will cause the Full Text Available indicators to appear for all records in the collection.
      It is recommended to set the value to No for Link in Record link type of collections as these are typically non-selective subscriptions and this will make sure that also non-ID content is flagged as available.

      It is recommended to keep the default setting Yes for Linkresolver link type of collections because setting the value to No may result in linking failures, if the collection in CDI contains additional content that is not reflected in the object portfolio list in Alma.

      Do not show as Full Text available in CDI even if active in Alma

      Select this option to suppress this collection when publishing holdings information to CDI. As a result, content will not be flagged as Full text available in the filtered search, unless it is also available from another collection where it is active and not suppressed. The collection will still appear on your link resolver, and users can link to the full text when coming from other search engines or platforms. 
      When a collection is ‘suppressed’, its content is also not searchable in the expand search, unless the collection set to active for search or unless the same content is available from other active collections.

      This option appears only for collections with either of the following settings:

      • The Available for CDI search Activation field is set to Yes.
      • The Available for CDI search Activation is set to No, but the collection has portfolios in Alma.

      Results:

      1. All portfolios for the collection are removed from the CDI holdings file. This will ensure that the content is not flagged as 'Full text available' unless it is also available from another collection where it is active and not suppressed. 
      2. The collection will still appear on your link resolver, and users can link to the full text when coming from other search engines or platforms. 
      3. Content from collections where the full text is suppressed is also not searchable in the expand search unless set to active for search or unless the same content is available from other active collections.
      4. The local bibliographic records are not affected and are published to the local Primo Index for discovery.

      Why use this option:

      1. Prevent content from certain collections from appearing in Primo results for example for Open Access collections – where you would like to have only the full text active for the link resolver, but you do not want the same full text visible in the filtered search in discovery because it could clutter the result lists for your users. 
      2. Prevent duplicate ebook results where bib records are published to Primo local and in addition the CDI records appear in the result list. This option will make sure that the CDI records do not appear in the result list. Note that this will also eliminate the chapter level records in CDI.

      View-Only Fields

      The following view-only fields from the registration system are also displayed on the tab:

      • CDI Collection ID – Used when publishing the CDI holdings file of the institution.

      • Number of records – number of records currently indexed in CDI. This number includes all versions (participants) of a resource and is updated for each collection twice a year in Alma.

        The number that appears for DBID searches in Primo/Primo VE may be smaller because it includes only one version of a resource and does not include records that do not have a subscription for search..

      • CDI update frequency – estimated update frequency of the collection in CDI. Values can be weekly, monthly, quarterly or yearly. The update frequency is based on the average update frequency of the last 12 months and is updated in Alma for each collection twice a year.

      • Full Text Rights in CDI – values are:

        • Open Access – All collections that do not require a subscription to access full text.
        • Subscription (Collection Level) – All collections that require a subscription for full text and are set to available on the collection level. They do not use the link resolver for selectively setting the collection content to available.
        • Subscription (Linkresolver) – All collections that require a subscription for full text and the availability setting is performed selectively on the item level, based on your link resolver activations.
           
      • CDI type - Type of database in CDI. Values can be:
        • A&I Database: Citation-only database. Records from the collection do not provide full text linking in CDI. 
          However, some of the records from the A&I database may be included in the CDI filtered search, with ‘Full text available’ indication, in case there are active portfolios in Alma from other collections.
        • Full Text Collection: Records from the collection provide full text linking in CDI.
        • Hybrid: Only part of the collection has a direct link to full text on the provider platform.

      • Newspapers – values are:

        • Yes – All collections with content that is available in both the Newspaper Search interface and the Regular Primo search interface.

        • Yes, Newspapers Search only – All collections with content that is available exclusively via the Newspaper Search interface, not via the Regular Primo search interface.

        • No – All collections that are not available using the Newspaper Search interface because they do not contain newspapers.

      • Available for CDI search activation – Yes indicates that at least 80% of the content of the collection is searchable in CDI. No indicates the data in the collection is not searchable or less than 80% of the content is searchable in CDI.

        For most of the collections, a data feed is received directly from the provider. For collections that are not directly indexed from the provider, CDI will automatically use the metadata from other collections in the index and the content will still be searchable.

      • Provider Coverage - Indicates how a collection is indexed in CDI.
        If set to ‘Yes’, the collection is indexed with data received directly from provider.
        If set to ‘No’, we do not get a database directly from the provider, but at least 80% of the content of the collection is covered in CDI by data received from other providers.

      • Resource Types – Lists up to 5 of the most frequently index resource types for the collection. This list is updated in Alma for each collection twice a year.

      • CDI Search Rights – Select Free for all collections whose content can be searched for free or Subscription for all collections that require a subscription for searching their content.

        CDI collections with Search Rights: Subscription require the patron in Primo VE to be logged in to retrieve search results from the collection.

      • CDI Full Text Linking – Indicates which type of link (collection level or link resolver) is needed to provide full text for a collection. Valid values are Link via Link resolver, Link in record, and Hybrid.

      For CDI records, in case the CDI full text linking is ‘Link in Record’ – the Alma link resolver is not invoked at all, the linking will use the link from the provider record directly. As a result, any configuration for services in Alma (name of the collection, display rules or sort order of services, as well as note information) is not used.

      • Coverage Percentage - Items that are available for CDI indicate the coverage percentage of the records in CDI. This indicator also includes the last date of calculation for this statistic. This information only displays if the coverage percentage has been calculated. If the date is not populated, it will not be displayed.

      • CDI Last Market Update - Last date that at least one record in the Electronic collection was updated in the CDI index. This field is currently updated quarterly.

        The CDI Last Market Updateis dynamic by nature, as CDI is continuously updated by many sources on an ongoing basis. Currently, the update frequency of this field is quarterly due to technical challenges. We are working to improve and automate this process, and our goal is to reach a 6-week update cycle by the end of , for all collections which are in CDI.

      CDI activation required – (only available when the CDI model is EasyActive)

      With the EasyActive setting, all collections are automatically searchable for the user and do not require search activation, except those listed in the EasyActive collection list. These collections do require activation in Alma (either via the ‘CDI only full text activation’ option or via regular Alma activation) and will in Alma get the indication ‘CDI activation required = Yes’.

      These collections will meet one of the following criteria:

      • The providers either do not want their content to be searchable automatically or their databases require subscriptions.
      • Some collections are likely to be used only by some institutions.

      What your users see in the filtered search is fully controlled by your full text activations in Alma. Additional search activations only impact the expanded search.

      For more information about this option, see: Managing Collections for Discovery with EasyActive

  • When you have completed your review, select Save or Contribute to Community (see Community Zone Contribution Guidelines for more information).

Modifying an Electronic Collection

This action is enabled only if the library set in the electronic resource matches the library defined on the user's role scope. For other electronic resources, this action is disabled. For details, see Library set on electronic resource.

To modify an electronic collection:

  1. Search for the electronic collection that you want to update.
  2. Select Edit Collection from the row actions list. The Electronic Collection Editor page appears.
  3. Update the fields on each tab of the Electronic Collection Editor page to match your requirements. For information on all tabs, see the Electronic Collection Editor Tabs and Fields table.
  4. Select Save to save your changes to the electronic collection.

Modifying an Electronic Service

When adding a service, Alma uses a wizard to obtain relevant information. You can use the Electronic Service Editor page to update this information on tabs that correspond to the steps of the wizard.

This action is enabled only if the library set in the electronic resource matches the library defined on the user's role scope. For other electronic resources, this action is disabled. For details, see Library set on electronic resource.

To modify a service:

  1. Search for the electronic collection that has the electronic service that you want to update.
  2. Select Edit from the row actions list. The Activation tab of the Electronic Service Editor page appears.
  3. Update the fields on each tab of the Electronic Service Editor page to match your requirements.
  4. Select Save to save your changes to the service.

Working with Database Type Electronic Collections

Electronic collections that rely primarily on an online database are set up somewhat differently from the primarily service-based package types.

Incorporating online databases in your inventory involves adding the database records to your inventory and performing inventory-related tasks. These collections are activated for patron discovery automatically once they have a defined URL and an associated unsuppressed bibliographic record.

Adding/changing an Electronic Collection Level URL (override) does not trigger Ongoing Discovery Indexing. The affected records need to be manually re-indexed for the change to take effect in Primo.

To add a local database to the inventory:

  1. Open the Electronic Collection Editor page (Resources > Create Inventory > Add Local Electronic Collection).
  2. Enter the initial database information. For more information, see the Initial Collection table.
    • For Collection Type, select Database.
    • For Service Type, select None (this is selected by default).
  3. Select Save and Continue. The Electronic Collection Description tab in the Electronic Collection Editor appears.
  4. Enter the information as described in the Electronic Collection Editor Tabs and Fields table. For the database to be available in Primo, you must enter at least a collection level URL and the additional descriptive information (the bibliographic record) on the Additional tab.
  5. After completing the information on the tabs, select Save. The Repository Search page appears with the database record that you added (see the figure below). With this record, you can process other tasks related to the online database such as placing an order.

To place an order for a database type of electronic collection

  1. Locate the database type of electronic collection for which you want to place an order.
  2. Select Order from the row actions list. The PO Line Owner and Type page appears.
  3. Enter the Purchase Type and PO Line Owner and select Create PO Line.
  4. Enter the PO line information for the online database. (See Creating PO Lines for additional information regarding these fields.)
  5. When you have completed entering the PO line information, select Order Now.

    When you have completed the order, the Purchase Order Lines in Review page appears and your usual acquisitions workflow can be completed.

    Once the order is complete, an electronic resource activation task is automatically added to the Electronic Resource Activation Task List. See Activating Electronic Resources for additional information. For a continuous order, you must select Done for this order in the task list to allow Alma to renew the order.

To confirm/verify the appearance of the database type of electronic collection in the discovery interface:

  1. Complete an All titles repository search for the online database.

    Locating the online database inventory record with an All titles search requires that the online database record includes a repository link. The repository link is entered on the Additional tab in the Additional descriptive information option.

  2. Select View It from the row actions list.
  3. Optionally, select Display in a new window.

To deactivate an electronic collection of type database:

  • To deactivate an electronic collection of type database, delete the URL from the electronic collection and suppress the bibliographic record. For customers using CDI, this ensures that the content from this database will no longer appear and will be flagged as Full text available in CDI, unless the CDI-only full text activation setting is used for the database. In this case, remove the CDI-only full text activation flag. To ensure the content of the collection will no longer be searchable (and appear in the CDI expanded search results), the collection should also be deactivated for search in CDI.

Linking a Local Electronic Collection to the Community Zone

You can link local electronic collections (including services and portfolios) to the Community Zone. This enables you to view the Community Zone updates for these electronic collections/portfolios.

When you initially link an electronic collection to the Community Zone, you can link the electronic collection, the service, and all the local portfolios. Once an electronic collection is linked to the Community Zone, you can link any local portfolios that are part of the electronic collection to Community Zone portfolios that are part of the electronic collection (see Linking a Local Portfolio that is part of a Community Zone-Linked Collection to the Community Zone for related information).

This is the first step in the process of linking resources to the Community Zone.

Alma executes the Link local electronic resources to the Community Zone job to process your linking request to the Community Zone. The results are available on the Monitor Jobs page (see Viewing Completed Jobs). For more information, see Viewing the Link Local Electronic Resources to the Community Zone Job Report.

Linking to community is supported only for collections with portfolios.
If your collection does not have portfolios, you can instead delete the collection and activate it from Community Zone. 

For more information about linking local electronic collections to the Community Zone, see the Link a Local Electronic Collection to a Community Zone Collection video ( mins).

To link a local electronic collection to the Community Zone:

  1. Search for a local electronic collection that you want to link to the Community Zone.
  2. Select Link to Community. The Link Electronic Resources to Community page appears. The page contains a general header with the electronic collection name, type of collection (selective package, aggregator package, or database), and vendor interface name (when available) and the following sections:
    • Local Information – Within this section, the following information is provided:
      • Service type (full text, selected full text, or none)
      • Total number of portfolios
      • Number of local portfolios
    • Community Information – Use this section to identify the name of the electronic collection to which you want to link in the Community Zone. Once you have specified this information, the Type, Interface name, and Service type information is updated based on the information provided by the Community Zone link.
    • Bibliographic Records Configuration – Use this section to identify how you want Alma to use the bibliographic record information available in the Community Zone. If you select Yes and a portfolio match is found in the Community Zone, the bibliographic record associated with the linked portfolio is the Community Zone bibliographic record. If you select No and a portfolio match is found in the Community Zone, the portfolio that is linked to the Community Zone portfolio will use the local bibliographic record. The match routine for this job uses either the ISSN or the ISBN identifier to confirm a match between the local portfolios in the electronic collection being linked with portfolios in the Community Zone.
  3. Using the browse capability of the Electronic collection name option, locate the electronic collection in the Community Zone to which you want to link.
  4. Select an electronic collection from the list of results.
    The Link Electronic Resources to Community page appears with your selection and related information.

    The fields in the Community Information section and the Bibliographic Records Configuration sections are dynamically updated once you have selected the electronic collection name from the Community Zone.

  5. Select Yes or No for the Use the community bibliographic records option and select Link. A dialog box appears with a summary/warnings regarding the linking selections that you made.
  6. Review the information in the dialog box and, if everything is okay, select Confirm. Alma displays a success message that the linking job (your request) was submitted. (This is the linking job that Alma automatically runs when you process a Community Zone link request, as described in the previous steps.)

Deleting Electronic Collections

The deletion is done by a background process, since it may be time consuming, if the number of portfolios in the collections is large. When the deletion process has been completed, Alma notifies you by an email. 

This action is enabled only if the library set in the electronic resource matches the library defined on the user's role scope. For other electronic resources, this action is disabled. For details, see Library set on electronic resource.

For information on deleting electronic collections of 'database' type, see Working with Database Type Electronic Collections.

To delete an electronic collection:

  1. Search for a electronic collection that you want to delete. 
  2. In the collection's list of row actions, select Delete. The Delete Confirmation message opens. 
  3. In the message, select how you want to handle bibliographic records without inventory:
    • Do nothing - leave the bib records in Alma as they are (without inventory)
    • Delete bibliographic records 
    • Suppress bibliographic records 
  4. Click Confirm. The process starts running. While it runs, the collection is displayed with a comment 'in deletion process', and without its list of row actions, to prevent users from performing any other changes on this collection. 
     
    deleting e www.buddysplantplus.com
    Electronic collection in the deletion process
  5. Go to Admin > Monitor Jobs. The Running tab opens showing the job status of the Delete Electronic Collection job. 
  6. Once the job completed running, select the History tab to view the job results.
  7. Select Report from the list of row actions to open the job report.
    deleting e collection www.buddysplantplus.com

Managing Local Portfolios

To manage local portfolios, you must have the following roles:
  • Electronic Inventory Operator
  • Electronic Inventory Operator Extended (required for delete operations)

A portfolio is the specific coverage, services, and link information relevant for a particular electronic title. Portfolios may be defined as standalone entities or as part of an electronic collection. Alma enables you to create and update portfolios separately from the workflow used to add local electronic collections. For more information on adding local electronic collections, see Adding a Local Electronic Collection.

Electronic Material Types

Portfolios have an electronic material type. The electronic material type is assigned to portfolios as follows:

  • For an electronic collection added by Ex Libris, the electronic material type of its associated portfolios is assigned automatically for the Electronic material type originating from Bib parameter. Alternatively, you can manually specify the type on the portfolio level using the Electronic material type parameter (see Electronic material type).
  • When you add a local standalone portfolio, you can select the material type.
  • When creating a new bibliographic record, the portfolio material is not taken into account. Thus, when you add a local portfolio and set a specific electronic material type, a bibliographic record is also created, but with 'Book' as the material, regardless of the portfolio's material. When adding ISSN, the material remains to be 'Book'. 

The possible types are:

  • Book
  • Journal
  • Dissertation
  • Proceeding
  • Conference
  • Report
  • Document - This type is sometimes used for portfolios in electronic collections in the Community Zone when the type is not otherwise know. If you see this type in a collection and believe that it is incorrect, please open a Salesforce case to correct it.
  • Series
  • Newspaper
  • Transcript
  • Database
  • Wire
  • CD-ROM
  • Manuscript
  • Sound Recording
  • Map
  • Other Visual Material - Includes slides and pictures.
  • Musical Score
  • Streaming Video
  • Streaming Audio
  • Data Set
  • Website
  • Video
  • Master Thesis
  • Government Document

Adding a Standalone Portfolio

You can add local standalone portfolios one at a time.

  • After you add a portfolio, you can locate it using the repository search and link it to a matching portfolio in the Community Zone. For more information, see Link to Community.
  • The maximum number of portfolios that an electronic collection can contain is , portfolios. This limit is recommended by Ex Libris for optimum performance. 

For more information about linking a standalone portfolio to an existing electronic collection using the Alma Electronic Resource Editor, refer to the Add a Single Standalone Portfolio to a Collection video ( mins).

To add a local portfolio:

  1. Open the New Portfolio page (Resources > Create Inventory > Add Local Portfolio).
  2. Enter the required portfolio information as described in the following table, when Portfolio Type is set to Standalone. (For a portfolio that is part of an electronic collection, see Adding Portfolios Individually to an Electronic Collection.)
    FieldDescription
    Descriptive Information:
    Creation TypeSelect to either create a new title or use an existing title.
    Record TypeThis parameter is available if Creation Type is Create new title. Select either One Time or Continuing.

    If you select One Time, the LDR of the created record will have m in pos. 7. If you select Continuing, the LDR of the created record will have s in pos. 7. Note that and pos. 23 will be o (online)

    Placement of new recordThis parameter is only available in a collaborative network. For information, see Selecting Where to Create New Bibliographic Records.

    Choose Title

    When you select Use an existing title, use the Choose Title parameter to select an existing title.

    Select the Select from a list icon to open the Repository Search page and select a bibliographic record.

    Title

    Enter a new title. This is required when you have selected Create a new title as the Creation Type.

    This identifies the name of the local portfolio that you are creating and is used to create the title ( field) in the bibliographic record for the portfolio that you are creating.

    Alternative Title 1Additional information if you created a new title.
    Alternative Title 2
    ISSN
    e-ISSN
    ISBN
    e-ISBN

    Record Format

    This field appears only if your institution supports multiple record formats such as MARC 21, KORMARC, UNIMARC, or CNMARC.

    From the drop-down list, select the type of format to be used when creating the bibliographic record for the portfolio that you are creating.

    Language (new portfolios only)

    When creating a new portfolio, select the portfolio language from the drop-down list. The default value is English for MARC 21 and blank/empty for KORMARC, UNIMARC, and CNMARC. Note that this parameter is only available when creating a new portfolio.

    The language information that you select for this parameter is placed in the new bibliographic record's (positions ) for MARC 21 / KORMARC and the 0# $a for UNIMARC / CNMARC.

    This parameter is optional. When it is left blank, the system places the following information in the bibliographic record that is created:

    • MARC eng
    • KORMARC: empty (the , positions are left blank)
    • UNIMARC / CNMAR: empty (the 0# $a is left blank)
    General Information:

    Portfolio Type

    Select Standalone or Part of an electronic collection.

    When you select "Part of an electronic collection", a popup opens where you need to select the electronic collection to which to link the portfolio. The selection screen that opens all collections, but allows selecting only the collections that match your role scope(s). For details, see Library set on electronic resource. 

    When linking a standalone portfolio that has a library set, and attaching it to an electronic collection that has a library set, the portfolio's library is deleted. When the library of the standalone portfolio and the library of the destination electronic collection are different, a warning is displayed on the collection selecting popup (see below): "The portfolio you are about to attach has a different library definition than the selected electronic www.buddysplantplus.com confirmed, the portfolio will inherit the electronic collection's library definition. Note that this action cannot be reversed."

    Electronic Collection (for part of an electronic collection)

    Enter the name of the electronic collection to which you want to link the local portfolio that you are creating. Select the Select from a list icon to open the search page and select the electronic collection from the repository.

    When you create a portfolio as a step in creating an electronic collection, the electronic collection link defaults to the one being created.

    Service (for part of an electronic collection)Enter the service (such as Full Text) for the selected electronic collection. When you select an electronic collection from the repository, the Service parameter is completed using the service identified for the electronic collection that you selected.
    Interface name (for standalone)Select a vendor interface for the standalone portfolio. Use the Select from a list icon to search from the available list of vendor interfaces.

    Library

    When you choose an electronic collection that this portfolio will be part of, and this electronic collection has a library set, then the "Library" parameter displays the library set on the selected electronic collection in read-only mode. If the collection does not have a library set, then you set a library for the portfolio. You can only select from libraries within your role's scope. For details, see Library set on electronic resource.

    COUNTER Platform

    Specify a COUNTER Platform for tracking usage information.

    See COUNTER Platform for more information.

    Coverage Information:
    Date Information:
    From YearCoverage field that indicate the content that was purchased/activated. These fields affect service resolution (such as Primo). Coverage appears in the repository search results (available from/until). This identifies the portfolio threshold.
    Until Year
    From Month
    Until Month
    From Day
    Until Day
    From Volume
    Until Volume
    From Issue
    Until Issue
    Embargo/Rolling Year:
    OperatorA moving wall of availability.
    Number of Years
    Number of Months
    Inventory and Linking Information:
    Parser

    (for part of an electronic collection)

    The necessary linking information (if these details are not the same as the electronic collection linking information).

    Example: EBSCO_HOST::ebsco_am

    This defaults to the parser information available with the electronic collection that you selected in the General section. For detailed information, see the Library-Specific Parameters table above and the SFX Target and Alma E-Collection Configuration Guide including the Introducing E-Collection Configuration for Alma chapter of this guide for its usage with Alma.

    Service parser parameters

    (for part of an electronic collection)

    The electronic collection’s parser parameters.

    Example:db_host=poh&ebscohosturl = www.buddysplantplus.com & linkurl=www.buddysplantplus.com & shib=$$SHIBBOLETH & customer_id=$$CUSTOMER_ID

    This defaults to the service’s parser parameters available with the electronic collection that you selected in the General section.

    Parser Parameters
    or
    URL
    Enter one of the following optional parameters as needed:
    • The portfolio-level parser parameters (part of an electronic collection), if this setting is different from the Service Parser Parameters previously identified (above). Alma uses the portfolio-level parser/parser parameters when they are different from the service-level parser/parser parameters.
    • The URL (standalone or part of an electronic collection) for accessing the portfolio. This URL overrides the URL created based on the parameters taken from the electronic collection, service, and portfolio.
    Proxy EnabledWhether the proxy is enabled.

    See the Resolver Proxies section for information regarding proxy relationships among portfolios, electronic collections, and services.

    Proxy SelectedA proxy profile option from the drop-down list. When you specify Yes for Proxy enabled, you must identify which proxy profile is used for authentication (of users outside the library’s network) to access the online database you have created. If you specify Yes for Proxy enabled and you make no selection from the Proxy selected drop-down list (that is, you leave the option blank), Alma automatically uses the default proxy you have configured.

    See the Resolver Proxies section for information regarding how to create a proxy profile. The procedure To configure a resolver proxy definition type of integration profile describes how to configure a default proxy profile.

    Availability StatusWhether the portfolio is active or inactive.
    Electronic material typeThe electronic material type from the drop-down list of options; see Electronic Material Types.
    Notes:
    Authentication NoteAdditional information related to authentication
    Public NoteA note regarding the portfolio that appears to patrons.
    Internal DescriptionAdditional information for staff regarding the portfolio.
  3. Select one of the following Save options.:
    • Save and Done – Save the portfolio information and close the New Portfolio page.
    • Save and Create Duplicate – Save the portfolio information and repopulate the New Portfolio page with the same information for you to edit for the next portfolio.
    • Save and Create New – Save the portfolio information and reopen the New Portfolio page for you to enter the next new local portfolio, thereby saving the steps of opening the New Portfolio page again manually.

    To view a video of the Save options, see Efficient Creation of Multiple Portfolios for a Bibliographic Record ( mins).

    Once you save a portfolio, you can test the link access using the OpenURL Link Resolver that displays results on the Electronic Services page. See Using the OpenURL Link Resolver Debugger Tool.

Adding Portfolios Individually to an Electronic Collection

You can add portfolios individually to electronic collections at any time.

To add a portfolio to an electronic collection:

  1. Open the New Portfolio page (Resources > Create Inventory > Add Local Portfolio).
  2. Enter the required portfolio information as described in the New Portfolio Page Options (Standalone and Electronic Collection) table in Adding a Standalone Portfolio, making sure that Portfolio Type is set to Part of an Electronic Collection and the associated electronic collection and service are specified. (For a standalone portfolio, refer to Adding a Standalone Portfolio.)
  3. Select one of the Save options.

Adding a Set of Standalone Local Portfolios to a Local Electronic Collection

By adding a set of standalone local portfolios to a local electronic collection service, you can more easily manage portfolios (activate, deactivate, export, and delete as a group versus individually, one at a time). Once portfolios are grouped into an electronic collection, you can use the portfolio loader capabilities to maintain the portfolios. (See Adding, Editing, or Removing Portfolio Information in Bulk for information about using Load Portfolios.)

Note that adding portfolios using a set is not an option for collections that are linked to the Community Zone.

To add a set of local standalone portfolios to a local electronic collection:

  1. Create a set of local standalone portfolios.
  2. To add the set of standalone portfolios to an existing local electronic collection, do the following or skip to step 3 to add portfolios to a new electronic collection.
    1. Complete a search to locate the existing local electronic collection.
    2. Select Edit Service and continue with step 4 below.
  3. To add the set of standalone portfolios to a new local electronic collection:
    1. On the Electronic Collection Editor page (Resources > Create Inventory > Add Local Electronic Collection), enter the Public name for the electronic collection and other details.

      You can specify the service type — Full Text, Selected Full Text, or None — on the Electronic Collection Editor page (eliminating additional steps to make this specification). Note that there is no functional implication to selecting Full Text or Selected Full Text. If None is selected (for databases), portfolios cannot be added.

    2. Select Save and Continue. The Electronic Service Editor page appears.
  4. Select the Portfolios tab.
  5. Select Add from set. The Add From Set page appears.
  6. Search/select the set name (that you created/saved in step 1).
  7. Select Submit and select Confirm for the confirmation message. The Electronic Service Editor page shows a job submitted message, and a System Job Notification message is emailed with the job details.
  8. Select Save. The Electronic Collection Editor page appears with an electronic collection successfully updated message.
  9. Select Portfolio List from the row actions list to view the standalone portfolios added to the electronic collection.

For end-result examples of where the Electronic Collection name appears in your search results in Alma and Primo related to the local portfolios that you’ve added to an electronic collection, see the Adding a Local Electronic Collection presentation.

Removing a Local Portfolio from an Electronic Collection

You can remove a local portfolio from an electronic collection. By removing a local portfolio from an electronic collection, you turn it into a standalone portfolio.

To remove a local portfolio from an electronic collection:

  1. Complete a repository search for the electronic collection containing the local portfolio that you want to remove.
  2. In your search results containing the local portfolio to remove, select Edit Service.
  3. Select the Portfolios tab. The electronic collection contents appear.
  4. Select the portfolio you want to remove and select Delete Selected, or select Remove from the row actions list.
  5. Select Save.

Using Portfolio Loader for Adding, Updating or Removing Portfolio Information in Bulk

You can create, update, and delete portfolios for an electronic collection in batch mode by uploading an Excel spreadsheet or a KBART file that contains a list of portfolios. For information, see Portfolio Loader (Excel file) or Portfolio Loader Support to KBART Files.

  • Related Portfolios can only be updated using the Portfolio Loader. Creation of Related Portfolios using the Portfolio Loader is not supported.
  • This action is enabled only if the library set in the electronic resource matches the library defined on the user's role scope. For other electronic resources, this action is disabled. For details about library inheritance by portfolios, see Library Set on Electronic Resource. 

The file upload wizard enables you to select whether to load the complete set of portfolios or just the ones that have been updated since the last load.

Refer to the following workflow diagram for a general understanding and illustration of the Portfolio Loader process:

Portfolio_Loader_www.buddysplantplus.com

Portfolio Loader Workflow

To add, update, or delete multiple portfolios using a batch process:

  1. From the Portfolios tab on the Electronic Service Editor page, select Load Portfolios.

    The Activation Wizard File Upload page appears.

  2. In the Format field, select the file type you are loading into the Portfolio Loader. For instance, select either the default Portfolio Loader Format (an Excel file) or KBART file.
  3. In the Select File section, enter the name and path of the Excel file (with either the .xls or .xlsx extension) or KBART file (with either the .tsv or .xsl extension ) you prepared, or select Browsebrowse_www.buddysplantplus.com to select the file.
    Select_File_Portfolio_www.buddysplantplus.com

    Select Format and File - Load Portfolios

  4. Select one of the following Loading Policy Types in the Select Loading Policy section:
    • Complete – Loads a complete set of portfolios, overwriting any existing portfolios. The following options are available when this is selected:
      • Add local portfolios – Process the portfolios (in the input Excel or KBART file) in the following manner:
        • If a match is found in the Community Zone for the portfolio, the portfolio is added and linked to the Community Zone.
        • If a match is not found in the Community Zone for the portfolio (based on the identifier), a match is attempted in the Institution Zone and, if found, the portfolio is added as a local portfolio in the electronic collection. Otherwise, a new local portfolio record is created and added to the electronic collection.
      • Update portfolios – Update existing local portfolios with the information listed in the Excel or KBART file for the matching portfolios when this option is selected. For portfolios linked to the Community Zone, only parser parameters and coverage information is updated when this option is selected.

        When updating local portfolios using the portfolio loader, the parser is always changed to Bulk:BULK.
        Verify that the URL type (override) is not set for Parser parameters if the Parser parameters (override) value is empty. Otherwise, the service results in an error.

      • Delete portfolios – Select this option to indicate that:
        • If portfolios are in the Community Zone-linked electronic collection and not in the Excel or KBART file, they will be deleted. These portfolios become local and are deactivated.
        • If portfolios are in the Excel or KBART file but not in the Community Zone-linked electronic collection, they will be activated from the Community Zone (if they exist in the Community Zone)
        This differs from how Alma processes the Excel or KBART file contents when the Delete option for the Incremental loading policy type is selected (see the description below).

        The Delete portfolios option provides the following additional options to enable you to specify how you want to handle bibliographic records when deleting portfolios results in bibliographic records without inventory:

        • Delete bibliographic record(s)
        • Suppress bibliographic record(s)
        • Do nothing
    • Incremental – Loads a file that includes only the incremental changes to the portfolio list of a specific electronic collection. With this option, you can load only the portfolios that have been updated since the last load.

      When you choose Incremental, the page refreshes to display the following incremental options:

      • Add New – This option adds new portfolios to existing collections in the following cases:
        • When the electronic collections are linked to the Community Zone and Add New is selected, this operation attempts to match titles in the Excel or KBART file with portfolios of the same collection in the Community Zone, and if found, activates the relevant portfolios. If no match is found, local portfolios are created.
        • When the electronic collection is local and Add New is selected, the portfolio loader adds the titles in the Excel or KBART file as local portfolios.
      • Update – This option updates the details of all electronic collection portfolios that are listed in the file.
      • Delete – When this option is selected, any portfolios that are in the Excel or KBART file that match the portfolios in the electronic collection are deleted from the repository.

        This differs from the Delete portfolios option under the Complete loading policy type (see the description above).

        The Delete option provides the following additional options to enable you to specify how you want to handle bibliographic records when deleting portfolios results in bibliographic records without inventory:

        • Delete bibliographic record(s)
        • Suppress bibliographic record(s)
        • Do nothing
        For this example, select Complete and Add local portfolios.

    For more information on the Alma portfolio loader, see Portfolio Loader.

  5. For Record Format, select the type of records to create.

    This field appears only if your institution supports multiple record formats (enabled by Ex Libris).

  6. Select the appropriate validation policy, according to the below guidelines:
    • Files up to ~2 MB can be validated online.
    • For files bigger than ~2 MB and up to 10 MB, select the Validate offline option. 
      Select one of these options:
      • Load file if there are no errors – If the validation completes (offline) with no errors, the portfolio records in the Excel or KBART file are uploaded and activated. If any lines have errors, the job completes successfully but no lines are uploaded or activated.
      • Load file – ignore lines with errors – If the validation completes (offline) with errors, the portfolio records in the Excel or KBART file with errors are ignored and the remaining portfolio records are uploaded and activated.
  7. Select Next.
    If there are validation errors in the Excel or KBART file, the Activation Wizard File Upload page specifies that errors exist. Correct the errors in your original Excel or KBART file and re-import/upload the file as described in the previous steps.

If the file has no validation errors, the Activation Wizard: Activation Summary page appears, displaying the number of portfolios to be activated as well as the number of portfolios to be created locally.

Portfolio Loader Support to KBART Files

The Portfolio Loader also supports the KBART format, which is used in institutions around the world for electronic resource exchange with vendors. To learn more about the KBART format, see here. 

Only specific KBART fields are supported by Alma. See List of Supported KBART Fields.

The types of KBART formats that are supported are *.tsv, *.txt, and *.xsl.

Uploading KBART Files in the Portfolio Loader

The "Format" option was added to the Portfolio Loader:

KBART option on the Portfolio Loader

KBART option on the Portfolio Loader

The following options are available:

  • Portfolio Loader Format (previously, the only option) - Select to upload an input file in the Excel format. For details, see Portfolio Loader. 
  • KBART - Select to upload an input file in the KBART format. 

List of Supported KBART Fields

The following KBART fields are supported by the Portfolio Loader:

") is only possible within an advanced condition (see advanced conditions).

Guide Activation Options

Important: These options are set at the guide level.

When adding a new condition, there are three main settings:

  • Enabled checkbox: Determines if the condition is active or inactive. If this is not checked, the condition will not be evaluated
  • Help Panel checkbox: Determines if the guide will be available from the OGL Help Widget
  • Autoload checkbox: Determines if the guide should start automatically if the condition is met

display conditions dialog

There are three types of conditions, these are:

  • Simple conditions
  • Advanced conditions
  • Time conditions

simple condition icon Simple Conditions

condition buttons

Simple conditions offer a simplified process of setting activation conditions by leveraging predefined pages and user roles. To set a new condition, click on the simple condition button, this will bring up the following interface:

simple condition example

There are five basic combinations in simple conditions, these are summarised in the table below:

Display WhenDescription
Always

settings for display always

Displays the guide in the widget, all the time.

Note: We recommended NOT to use the Autoload option with this type of condition.

Page IS

settings for display when page is

Displays the guide in the widget only when the user is on the Homepage

Note: If the Autoload option is used, the recommendation is to add additional conditions to limit the number of times the guides will autoload (see advanced conditions).

Page IS NOT

setting for display when page is not

Displays the guide in the widget only when the user is not on the Homepage

Note: We recommended NOT to use the Autoload option with this type of condition.

Role IS

settings for display when role is

Displays the guide in the widget only when the user role is = Payables Specialist

Note: Simple conditions (AND conditions) allow you to associate only one user group (i.e. Payables Specialists) to the guide. If you add multiple simple conditions to the same guide(i.e. a condition for Payables Specialists and another for Receivables Specialists), then all conditions will have to be met for the guide to be displayed in the widget or autoloaded (that is, a user will have to be both a Payables Specialist and a Receivables Specialist). Conditions (OR conditions) that allow the user to be either a Receivables Specialist or Payables Specialist are covered in advanced conditions.

Role IS NOT

settings for display when role is not

Displays the guide in the widget only when the user role is not = Payables Specialist

Remember: Multiple conditions are joined by the Boolean AND operator. All conditions have to be TRUE for the guide to be activated accordingly (help widget/autoload).

advanced condition icon Advanced Conditions

condition buttons

Advanced conditions offer a variety of options in setting activation conditions, this includes multiple user roles. To set a new condition, click on the advanced condition button, this will bring up the following interface:

advanced condition UI

There are four basic combinations in advanced conditions, these are:

  • Page has / Page has NOT
  • User has / User has NOT

Options within Page HAS / Page HAS NOT:

when page options

Display When Page has / Display When Page has NOT Description
URL matching

settings for url matching

Will match against any part of the page's address. You can use regular expressions as well. Use any javascript regular expression by surrounding it with [ ] brackets. For example: [product_id=1.*] will match all URL with product_id's that starts with 1.

Note: Use the exact check box if you want the entire path to match exactly with the provided value. Note that the domain (e.g. www.buddysplantplus.com_www.buddysplantplus.com) will be ignored in this evaluation.

FUSION APPLICATIONS:

Display Guide Only on Certain Pages

  • You can display guides based on all or part of the URL of the HTML application. For Oracle Fusion, the literal URL string that you see in your browser is not used. Instead, use the page route, which is a descriptive string that substitutes for the URL.

    You can find the Route by using the Google Chrome DevTools Console. Go to a page in the application, then enter www.buddysplantplus.comte() in the browser console. You can use all or part of the route to identify the page.

    finding the route in chrome console

Note that if the Route is saved in Pages, OGL will automatically convert the condition to a Simple condition.

URL parameter

settings for url parameter

Will match against a specific URL parameter. You can either test that the specific URL parameter exists or evaluate its value.

variable

settings for variable

Will match against a javascript variable. You can either test the existence of a variable or test its actual value.

cookie

settings for cookie

Will match against a browser cookie. You can either test the existence of a cookie or test its actual value.

session variable

settings for session variable

Will match against a special OGL variable. The OGL javascript API allows setting session variables that exist only throughout the duration of the currently logged in user. You can then condition your guides to display based on these variables.

element

settings for element

Will match against any element on the page's Document Object Model (DOM). You can also extend this condition by telling iridize to wait for multiple objects matching the provided selector.

visible element

settings for visible element

Will match against a visible element on the page's Document Object Model (DOM). This is more restrictive than an element condition because in HTML an element can be invisible.

Options within User HAS / User HAS NOT:

when user options

Display When User has / Display When User has NOT Description
field

settings for field

Will match against a user-specific field as it was relayed to OGL using the www.buddysplantplus.com call. You can either test the existence of a user field or test its actual value. Use this to govern your guides based on user roles, permission level, or even geolocation.

Note: The required field has to be set/read in the OGL JavaScript. Please contact us for support.

Multiple User Roles

To set role conditions, the roles must be defined in JavaScript or in the Oracle Fusion configuration. Advanced conditions allow you to associate multiple user roles to a guide/a group of guides utilizing the OR operator.

When you create a field (i.e. user_role) matching condition you can use a regular expression. To tell OGL that the string is a regular expression surround it with square brackets [].

So, let's say you have the following roles in your application: Line Manager, HR Executive, HRAdministrator

As per OGL requirements, these roles are given shortened reference names, to accommodate the 90 character limit of the field. So the above roles are translated to line_mgr, hr_exec, hr_admin.

To show an OGL item guide only if the user has or has NOT either of the three roles, the advanced activation condition would be as follows:

settings for field example

seen guide

settings for seen guide

Will display the current OGL item (in the widget or autoload) if the user has seen the provided guide (i.e Create Requisition from Catalog) X number of times in the past.

Note: If you have guides A, B, and C, you can set the condition such that:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOT seen guide A/B/C more than/less than/exactly X number of times.

seen guide (timed)

settings for timed seen guide

This type of condition is similar in essence to the seen guide condition but it is based on how long ago the user last saw the provided guide (i.e Create Requisition from Catalog) instead of the number of times a user has seen the provided guide.

Note: If you have guides A, B, and C, you can set the condition such that:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOTseen guideA/B/C more than X number of seconds ago.

advanced in guide

settings for advanced in guide

Will match if the user has engaged with the guide at least once. A user is considered to have engaged with a guide if and only if s/he has advanced past the first step in the guide.

Note: If you have guides A, B, and C, you can set the condition such that:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOTadvanced in guideA/B/C

advanced in guide (timed)

settings for timed advanced in guide

This type of condition is similar in essence to the advanced in guide condition but it is based on how long ago the user last advanced past the first step in the provided guide (i.e Create Requisition from Catalog) instead of the number of times a user has advanced in the provided guide.

Note: If you have guides A, B, and C, you can set the condition such that it is:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOTadvanced in guideA/B/C more than seconds ago.

closed guide

settings for closed guide

Will match if the user has decided to manually close the guide by clicking on the 'X' button located at the top-right corner of one of the tooltips.

closed guide (timed)

settings for timed closed guide

This type of condition is similar in essence to the closed guide condition but it is based on how long ago the user last closed the guide.

Note: If you have guides A, B, and C, you can set the condition such that it is:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOTclosed guideA/B/C more than seconds ago. Clicking the Remind me later button does not count as closing the guide.

finished guide

settings for finished guide

Will match if the user has gone through the whole guide from start to finish.

Note: If you have guides A, B, and C, you can set the condition such that it is:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOTfinished guideA/B/C.

finished guide(timed)

settings for timed finished guide

This type of condition is similar in essence to the finished guide condition but it is based on how long ago the user last finished the guide.

Note: If you have guides A, B, and C, you can set the condition such that it is:

Guide A is displayed in the widget and/or autoloaded When the User has or has NOTfinished guideA/B/C more than seconds ago.

advanced in or closed the guide

settings for advanced in or closed the guide

This condition is a combination of the Advance in Guide and the Closed Guide conditions. It will match if the user has either engaged with the guide or closed it manually.

Note: The Remind me later button does not count as closing the guide. So using this condition in combination with the Seen Guide condition "completes" the remind me later functionality.

time icon Time Condition

condition buttons

A time condition allows you to set when and for how long a guide should be displayed in the widget or autoloaded. In the example below the guide is set to display for a period of seven days, commencing on February 26,

example time condition

Important: The time condition does not auto-adjust for different time zones, if the target audience is in a different time-zone to the person setting the condition, the difference in time needs to be considered and where necessary, adjusted by the person setting the condition.

OGL Standard Roles

Click here to download a list of Role mappings.

Autosegmentation

Autosegmentation is the process by which guides can be started on any page in the process and only works on Oracle Fusion applications. When selecting a guide from the widget, it will begin on the first step on the page that the user is on. In addition, the account and &#x;if used, the embedded JavaScript-- must be configured for auto segmentation. Contact Oracle University to verify that your account is properly configured.

Autosegmentation occurs automatically. As you select elements while creating guides, OGL stores the page location (or Route). OGL then uses those pages to build the default Activation Condition for the guide. The auto segmentation pages are used instead of a standard URL to identify the pages where the guide can be run. The following image shows the Activation Condition automatically created by auto segmentation (this condition is identifiable by the Auto-Generated tag):

example settings for autosegmentation

To ensure auto segmentation works as intended, we recommend you do not change the default activation condition.

The following list provides recommendations for improving the security ("hardening") of your Tableau Server installation.

Security updates are included in the latest versions and maintenance releases (MR) of Tableau Server. You cannot install security updates as patches. Rather, you must upgrade to a current version or MR to update Tableau Server with the latest security fixes.

Always reference the most current version of this topic after upgrading. The current version includes in the topic URL.

1. Update to the current version

We recommend that you always run the latest version of Tableau Server. Additionally, Tableau periodically publishes maintenance releases of Tableau Server that include fixes for known security vulnerabilities. (Information regarding known security vulnerabilities can be found on the Tableau Security Bulletins page and the Salesforce Security Advisories(Link opens in a new window) page.) We recommend that you review maintenance release notifications to determine whether you should install them.

To get the latest version or maintenance release of Tableau Server, visit the Customer Portal(Link opens in a new window) page.

2. Configure SSL/TLS with a valid, trusted certificate

Secure Sockets Layer (SSL/TLS) is essential for helping to protect the security of communications with Tableau Server. Configure Tableau Server with a valid, trusted certificate (not a self-signed certificate) so that Tableau Desktop, mobile devices, and web clients can connect top the server over a secured connection. For more information, see SSL.

3. Disable older versions of TLS

Tableau Server uses TLS to authenticate and encrypt many connections between components and with external clients. External clients, such as browsers, Tableau Desktop, Tableau Mobile connect to Tableau using TLS over HTTPS. Transport layer security (TLS) is an improved version of SSL. In fact, older versions of SSL (SSL v2 and SSL v3) are no longer considered to be adequately secure communication standards. As a result, Tableau Server does not allow external clients to use SSL v2 or SSL v3 protocols to connect.

We recommend that you allow external clients to connect to Tableau Server with TLS v and TLS v

TLS v is still regarded as a secure protocol and many clients (including Tableau Desktop) do not yet support TLS v

TLS v capable clients will negotiate TLS v even if TLS v is supported by the server.

The following tsm command enables TLS v and v (using the "all" parameter) and disables SSL v2, SSL v3, TLS v1, and TLS v (by prepending the minus [-] character to a given protocol). TLS v is not yet supported by all components of Tableau Server.

To modify the protocols that govern SSL for the Tableau Server PostgreSQL repository, see www.buddysplantplus.comsuite.

You can also modify the default list of cipher suites that Tableau Server uses for SSL/TLS sessions. For more information see the www.buddysplantplus.comsuite section at tsm configuration set Options.

4. Configure SSL encryption for internal traffic

Configure Tableau Server to use SSL to encrypt all traffic between the Postgres repository and other server components. By default, SSL is disabled for communications between server components and the repository. We recommend enabling internal SSL for all instances of Tableau Server, even single-server installations. Enabling internal SSL is especially important for multi-node deployments. See Configure SSL for Internal Postgres Communication.

5. Enable firewall protection

Tableau Server was designed to operate inside a protected internal network.

Important: Do not run Tableau Server, or any components of Tableau Server on the internet or in a DMZ. Tableau Server must be run within the corporate network protected by an internet firewall. We recommend configuring a reverse proxy solution for internet clients that need to connect to Tableau Server. See Configuring Proxies for Tableau Server.

A local firewall should be enabled on the operating system to protect Tableau Server in single and multi-node deployments. In a distributed (multi-node) installation of Tableau Server, communication between nodes does not use secure communication. Therefore, you should enable firewalls on the computers that host Tableau Server.

To prevent a passive attacker from observing communications between nodes, configure a segregated virtual LAN or other network layer security solution.

See Tableau Services Manager Ports to understand which ports and services Tableau Server requires.

6. Restrict access to the server computer and to important directories

Tableau Server configuration files and log files can contain information that is valuable to an attacker. Therefore, restrict physical access to the machine that is running Tableau Server. In addition, make sure that only authorized and trusted users have access to the Tableau Server files in the directory.

7. Update the Tableau Server Run As User account

By default, Tableau Server runs under the predefined Network Services (NT Authority\Network Service) Windows account. Using the default account is acceptable in scenarios where Tableau Server does not need to connect to external data sources that require Windows authentication. However, if your users require access to data sources that are authenticated by Active Directory, update the Run As User to a domain account. It's important to minimize the rights of the account that you use for the Run As User. For more information, see Run As Service Account.

8. Generate fresh secrets and tokens

Any Tableau Server service that communicates with repository or the cache server must first authenticate with a secret token. The secret token is generated during Tableau Server setup. The encryption key that internal SSL uses to encrypt traffic to Postgres repository is also generated at during setup.

We recommend that after you install Tableau Server, you generate new encryption keys for your deployment.

These security assets can be regenerated with the command.

Run the following commands:

9. Disable services that you're not using

To minimize the attack surface of the Tableau Server, disable any connection points that are not needed.

JMX Service

JMX is disabled by default. If it's enabled but you're not using it, you should disable it by using the following:

Verify session lifetime configuration

By default, Tableau Server does not have an absolute session timeout. This means that browser-based client (Web authoring) sessions can remain open indefinitely if the Tableau Server inactivity timeout is not exceeded. The default inactivity timeout is minutes.

If your security policy requires it, you can set an absolute session timeout. Be sure to set your absolute session timeout in a range that allows the longest-running extract uploads or workbook publishing operations in your organization. Setting the session timeout too low may result in extract and publishing failures for long-running operations.

To set the session timeout run the following commands:

, where value is the number of minutes. The default is , which is 24 hours.

, where value is the number of minutes. The default is

Sessions for connected clients (Tableau Desktop, Tableau Mobile, Tableau Prep Builder, Bridge, and personal access tokens) use OAuth tokens to keep users logged in by re-establishing a session. You can disable this behavior if you want all Tableau client sessions to be solely governed by the browser-based session limits controlled by the commands above. See Disable Automatic Client Authentication.

Configure a server allowlist for file-based data sources

By default, Tableau Server allows authorized Tableau Server users to build workbooks that use files on the server as file-based data sources (such as spreadsheets). In this scenario, files are accessed by the Run As Service Account.

To prevent unwanted access to files, we recommend that you configure allowlist functionality. This lets you limit the Run As service account to just the directory paths where you host data files.

  1. On the computer running Tableau Server, identify the directories where you will host data source files.

    Important Make sure the file paths you specify in this procedure exist on the server. If the paths do not exist when the computer starts, Tableau Server will not start.

  2. Run the following commands:

    , where path is the directory to add to the allowlist. All subdirectories of the specified path will be added to the allowlist. If you want to specify multiple paths, separate them with a semicolon, as in this example:

Enable HTTP Strict Transport Security for web browser clients

HTTP Strict Transport Security (HSTS) is a policy configured on web application services, such as Tableau Server. When a conforming browser encounters a web application running HSTS, then all communications with the service must be over a secured (HTTPS) connection. HSTS is supported by major browsers.

For more information about how HSTS works and the browsers that support it, see The Open Web Application Security Project web page, HTTP Strict Transport Security Cheat Sheet(Link opens in a new window).

To enable HSTS, run the following commands on Tableau Server:

By default, HSTS policy is set for one year ( seconds). This time period specifies the amount of time in which the browser will access the server over HTTPS. You should consider setting a short max-age during initial roll-out of HSTS. To change this time period, run . For example, to set HSTS policy time period to 30 days, enter .

Disable Guest access

Core-based licenses of Tableau Server include a Guest user option, which allows any user in your organization to see and interact with Tableau views embedded in web pages.

Guest user access is enabled by default on Tableau Servers deployed with core-based licensing.

Guest access allows users to see embedded views. The Guest user cannot browse the Tableau Server interface or see server interface elements in the view, such as user name, account settings, comments, and so on.

If your organization has deployed Tableau Server with core licensing and Guest access is not required, then disable Guest access.

You can disable Guest access at the server or site level.

You must be a server administrator to disable the Guest account at either the server or the site level.

To disable Guest access at the server level:

  1. In the site menu, click Manage All Sites and then click Settings > General.

  2. For Guest Access, clear the Enable Guest account check box.

  3. Click Save.

To disable Guest access for a site:

  1. In the site menu, select a site.

  2. Click Settings, and on the Settings page, clear the Enable Guest account check box.

For more information, see Guest User.

Beginning in , Tableau Server includes the ability to configure Referrer-Policy HTTP header behavior. This policy is enabled with a default behavior that will include the origin URL for all "secure as" connections (), which sends origin referrer information only to like connections (HTTP to HTTP) or those that are more secure (HTTP to HTTPS).

However, we recommend setting this value to , which only sends referrer information to same-site origins. Requests from outside the site will not receive referrer information.

To update the referrer-policy to , run the following commands:

For more information about configuring additional headers to improve security, see HTTP Response Headers.

Configure TLS for SMTP connection

Beginning in , Tableau Server includes the ability to configure TLS for the SMTP connection. Tableau Server only supports STARTTLS (Opportunistic or Explicit TLS).

Tableau Server can be optionally configured to connect to a mail server. After configuring SMTP, Tableau Server can be configured to email server administrators about system failures, and email server users about subscribed views and data-driven alerts.

To configure TLS for SMTP:

  1. Upload a compatible certificate to Tableau Server. See tsm security custom-cert add.
  2. Configure TLS connection using TSM CLI.

    Run the following TSM commands to enable and force TLS connections to the SMTP server and to enable certificate verification.

    By default, Tableau Server will support TLS versions 1, , and , but we recommend that you specify the highest TLS version that the SMTP server supports.

    Run the following command to set the version. Valid values are , ,, , and . The following example sets the TLS version to version

    For more information about other TLS configuration options, see Configure SMTP Setup.

  3. Restart Tableau Server to apply changes. Run the following command:

Configure SSL for LDAP

If your Tableau Server deployment is configured to use a generic LDAP external identity store, we recommend configuring SSL to protect authentication between Tableau Server and your LDAP server. See Configure Encrypted Channel to LDAP External Identity Store.

If your Tableau Server deployment is configured to use Active Directory, we recommend enabling Kerberos to protect authentication traffic. See Kerberos.

Scope permissions for non-default installation locations

If you install Tableau Server on Windows to a non-default location then we recommend manually scoping the permissions on the custom installation directory to reduce access.

By default, Tableau Server will install on the system drive. The drive where Windows is installed is the system drive. In most cases, the system drive is the C:\ drive. In this default case, Tableau Server will install into the following directories:

However, many customers install onto a non-system drive or into a different directory. If you selected a different installation drive or directory location during Setup, then the data directory for Tableau Server will install into the same path.

To scope permissions on the custom installation directory, only the following accounts should have the corresponding permissions on the installation folder and all subfolders:

Set permissions for this account: Permissions required
The user account that is used to install and upgrade Tableau ServerFull control
The user account that is used to run TSM commandsFull control
System accountFull control
Run As service account, Network Service, and Local ServiceRead & execute

A procedure for setting these permissions can be found at Installing in a non-default location.

Change List

DateChange
May Added clarification: Do not disable REST API in organizations that are running Tableau Prep.
May Added recommendation for referrer-policy HTTP header.
June Removed recommendation to disable Triple-DES. As of version , Triple-DES is no longer a default supported cipher for SSL. See What's Changed - Things to Know Before You Upgrade.
January Added recommendation to configure TLS for SMTP.
February Added recommendation to configure SSL for LDAP server.
May Added TLS v to the disabled list of TLS ciphers. Added clarification to introduction about topic versioning.
August Added scoped permissions for non-default installations on Windows
October Added TLS v as a default supported cipher.
January Added clarification: All products enabled by the Data Management license require REST API.
February Removed recommendation to disable REST API. The API is now used internally by Tableau Server and disabling it may limit functionality.

SnapGene Viewer

View, annotate and share sequence files with the free SnapGene Viewer.
To edit, align and clone sequences, try the full version of SnapGene.

Try SnapGene

Your download will be available immediately.

Gain Unparalleled Visibility of Your Plasmids

With SnapGene Viewer you can view plasmid maps, annotate features, and share sequences with your colleagues for free. And when you want to do more, subscribe to SnapGene to simulate cloning and PCR, validate sequenced constructs and customize your plasmids.

What are the differences between SnapGene and SnapGene Viewer?

SnapGene Viewer

Free software that allows you to create, browse,
and share richly annotated sequence files.

Download now

SnapGene

The easiest way to plan, visualize and document
your everyday molecular cloning procedures.

Try for Free

View plasmid maps and sequence trace files

Annotate features on your plasmids

Share your sequences with colleagues

Sequence editing and alignment

Simulate cloning, PCR and mutagenesis

Customize annotations and enzyme sets

Automatically create graphical history

Discover the most user-friendly molecular biology experience

Try for Free

';} ?>

010 editor review Activators Patch

0 Comments

Leave a Comment