7 results found

1. Docline Citation not importing volume/issue numbers.

   The volume/issue and pages blank are not being imported when there are non-numeric values in the Citation field such as supplemental issues and e-page numbers.

   Bug# 6539

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Docline  ·  Delete…  ·  Admin →
   released  ·  AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded

   Released in ILLiad 9.2

2. Docline script error causes a blank Account Type box to appear on the Docline Importing tab

   External systems running on the user's machine such as McAfee AntiVirus can affect web traffic. Since Docline is running through the web, users may receive a script error upon login. If the user clicks No or closes the script error, they will receive a blank Account Type box.

   Bug# 4111
   v8.7.3 and Docline 6.0

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docline  ·  Edit…  ·  Delete…  ·  Admin →
   released  ·  AdminSara Juel (Access Services Product Manager, Atlas Systems, Inc.) responded

   Released in DOCLINE 3.1.2.1 Scripts

3. ILLiad does not load new DOCLINE scripts that are installed by the auto-updater

   When ILLiad loads individual DOCLINE scripts for execution, it is loading the copies of the scripts located in Program Files that are not updated by the auto-updater. This means ILLiad loads the old DOCLINE scripts instead of the new ones, even after the auto-updater has run.

   Workaround: Replace the contents of C:\Program Files (x86)\ILLiad\Docline\ with the contents of C:\ProgramData\ILLiad\Docline after the auto-updater installs the new scripts.

   Bug# 11198

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docline  ·  Edit…  ·  Delete…  ·  Admin →
   released  ·  AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded

   Released in ILLiad 9.2

4. Docline scripts not importing patron name if it is in the imported info

   Bug#4263
   v9.0.3 & 8.7.3

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docline  ·  Edit…  ·  Delete…  ·  Admin →
   released  ·  AdminSara Juel (Access Services Product Manager, Atlas Systems, Inc.) responded

   Released in DOCLINE 3.1.2.1 Scripts

5. ILLIad drops "x" value at the end of ISSN when importing from Docline

   On both the borrowing and lending side, if the imported the citation and the ISSN end with an X, then the ISXN field in the transactions table leaves off the X in the borrowing Transaction record.

   Bug# 4027
   v9.0.3 & 8.7.3

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docline  ·  Edit…  ·  Delete…  ·  Admin →
   released  ·  AdminSara Juel (Access Services Product Manager, Atlas Systems, Inc.) responded

   Released in DOCLINE 3.1.2.1 Scripts

6. Default shipping value for articles being set to default shipping value of loans

   When the lending library imports the lending request, it puts the LenderAddresses.DefaultShippingMethodLoan value into the Transactions.ShippingOptions field instead of using the LenderAddresses.DefaultShippingMethodArticle value. v9.0.3 & 8.7.3

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docline  ·  Edit…  ·  Delete…  ·  Admin →
   released  ·  AdminSara Juel (Access Services Product Manager, Atlas Systems, Inc.) responded

   Released in ILLiad 9.1

7. Default primary DeliveryMethod are not not set to Odyssey

   The search and fill button is not filling in the Primary Delivery method correctly because Illiad is using the default from the FieldTranslation.xml file instead of the Docline Borrowing settings if the ShippingOptions value is left blank in the request. For example, the drop-down is set to Email PDF instead of Odyssey. While the default delivery methods are updated in ILLiad and the default FieldTranslation.xml files, the DeliveryMethods are not set to Odyssey, since the update doesn't automatically overwrite the FieldTranslation.xml file. This prevents the update from overwriting any customizations your site may have.

   Workaround: To change how ILLiad handles the shipping options value if the field is left blank in the request, choose one of the following options and make the appropriate changes to the FieldTranslation.xml file:

   Option 1- To not alter the drop-down when ILLiad fills out the request and leave the field as is, comment out the DeliveryMethod translation.

   Change This:

   <TranslationMap Type="DataSource" Name="DeliveryMethod" Target="OptionMap.NetworkShippingOption"/>

   To This:

   <!--<TranslationMap Type="DataSource" Name="DeliveryMethod" Target="OptionMap.NetworkShippingOption"/>-->v9.0.3

   Option 2- To continue trying to set based on the value in the ILLiad request, change the DefaultValue in the OptionMap for NetworkShippingOption.

   Change This:

   <OptionMap Name="NetworkShippingOption" DataSource="Transaction.ShippingOptions" DefaultValue="email_pdf">
   <Option SourceValue="E-mail" OptionValue="email_pdf"/> <!-- E-mail (PDF) -->
   <Option SourceValue="Article Exchange" OptionValue="article_exchange"/> <!-- E-mail (TIFF) -->
   <Option SourceValue="Fax" OptionValue="fax"/> <!-- Fax -->
   <Option SourceValue="Mail" OptionValue="mail"/> <!-- Mail -->
   <Option SourceValue="Odyssey" OptionValue="odyssey"/> <!-- Odyssey -->
   <Option SourceValue="Pickup" OptionValue="pickup"/> <!-- Pickup -->
   <Option SourceValue="Web" OptionValue="web_pdf"/> <!-- Web -->
   </OptionMap>

   To This:

   <OptionMap Name="NetworkShippingOption" DataSource="Transaction.ShippingOptions" DefaultValue="odyssey">
     <Option SourceValue="E-mail" OptionValue="email_pdf"/> <!-- E-mail (PDF) -->
     <Option SourceValue="Article Exchange" OptionValue="article_exchange"/> <!-- E-mail (TIFF) -->
     <Option SourceValue="Fax" OptionValue="fax"/> <!-- Fax -->
     <Option SourceValue="Mail" OptionValue="mail"/> <!-- Mail -->
     <Option SourceValue="Odyssey" OptionValue="odyssey"/> <!-- Odyssey -->
     <Option SourceValue="Pickup" OptionValue="pickup"/> <!-- Pickup -->
     <Option SourceValue="Web" OptionValue="web_pdf"/> <!-- Web -->
   </OptionMap>
   

   v9.0.3 & 8.7.3
   Bug#4081 & 4025

   The search and fill button is not filling in the Primary Delivery method correctly because Illiad is using the default from the FieldTranslation.xml file instead of the Docline Borrowing settings if the ShippingOptions value is left blank in the request. For example, the drop-down is set to Email PDF instead of Odyssey. While the default delivery methods are updated in ILLiad and the default FieldTranslation.xml files, the DeliveryMethods are not set to Odyssey, since the update doesn't automatically overwrite the FieldTranslation.xml file. This prevents the update from overwriting any customizations your site may have.

   Workaround: To change how ILLiad handles… more

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Docline  ·  Edit…  ·  Delete…  ·  Admin →
   released  ·  AdminSara Juel (Access Services Product Manager, Atlas Systems, Inc.) responded

   Released in DOCLINE 3.1.2.1 Scripts