Docs: Convert existin anchors to Antora syntax

Signed-off-by: Remington Steed <rjs7@calvin.edu>

diff --git a/docs-antora/modules/admin/pages/actiontriggers.adoc b/docs-antora/modules/admin/pages/actiontriggers.adoc
index 574c049..24e0358 100644 (file)
--- a/docs-antora/modules/admin/pages/actiontriggers.adoc
+++ b/docs-antora/modules/admin/pages/actiontriggers.adoc
@@ -17,7 +17,7 @@ You must have Local Administrator permissions to access the Action Triggers modu
 You will notice four tabs on this page: <<event_definitions, Event Definitions>>, <<hooks, Hooks>>, <<reactors, Reactors>> and <<validators, Validators>>.
 
 
-anchor:event_definitions[]
+[#event_definitions]
 
 === Event Definitions ===
 
@@ -153,7 +153,7 @@ image::media/test_event_def_output.png[Test Output]
 
 WARNING: If you are testing an email or SMS notification, use a test account and email as an example. Using the Test feature will actually result in the notification being sent if configured correctly.  Similarly, use a test item or barcode when testing a circulation-based event like Mark Lost since the test will mark the item as lost.
 
-anchor:hooks[]
+[#hooks]
 
 ==== Hooks ====
 Hooks define the Fieldmapper class in the core_type column off of which the rest of the field definitions ``hang''.
@@ -170,7 +170,7 @@ Hooks define the Fieldmapper class in the core_type column off of which the rest
 You may also create, edit and delete Hooks but the Core Type must refer to an IDL class in the fm_IDL.xml file.
 
 
-anchor:reactors[]
+[#reactors]
 
 ==== Reactors ====
 
@@ -187,7 +187,7 @@ Reactors link the trigger definition to the action to be carried out.
 You may also create, edit and delete Reactors. Just remember that there must be an associated subroutine or module in the Reactor Perl module.
 
 
-anchor:validators[]
+[#validators]
 
 ==== Validators ====
 

diff --git a/docs-antora/modules/admin/pages/sip_server.adoc b/docs-antora/modules/admin/pages/sip_server.adoc
index 1f9d432..446a73b 100644 (file)
--- a/docs-antora/modules/admin/pages/sip_server.adoc
+++ b/docs-antora/modules/admin/pages/sip_server.adoc
@@ -348,7 +348,7 @@ preceded with a 2-character field identifier) are used. The fields vary between
 | 99-98  | SC-ACS Status       | Yes                   |<<sip_99-98_sc_and_acs_status, 99/98_SC_and_ACS_Status>> 
 |===========================================================================
 
-anchor:sip_01_block_patron[]
+[#sip_01_block_patron]
 
 ==== 01 Block Patron ====
 
@@ -388,7 +388,7 @@ The response is a 24 ``Patron Status Response'' with the following:
 * Screen Message 1 (AF): _blocked_ 
 * Patron 
 
-anchor:sip_09-10_checkin[]
+[#sip_09-10_checkin]
 
 ==== 09/10 Checkin ====
 
@@ -452,12 +452,12 @@ Don't be confused by the different branches that can show up in the same respons
 * CT is the _destination location_ (i.e., pickup lib for a hold or target lib for a transfer). 
 ===============
 
-anchor:sip_11-12_checkout[]
+[#sip_11-12_checkout]
 
 ==== 11/12 Checkout ====
 
 
-anchor:sip_15-16_hold[]
+[#sip_15-16_hold]
 
 ==== 15/16 Hold ====
 
@@ -465,7 +465,7 @@ Evergreen supports the Hold message for the purpose of canceling
 holds.  It does not currently support creating hold requests via SIP2.
 
 
-anchor:sip_17-18_item_information[]
+[#sip_17-18_item_information]
 
 17/18 Item Information 
 ^^^^^^^^^^^^^^^^^^^^^^
@@ -501,12 +501,12 @@ EXTENSIONS: The CT field for _destination location_ and CS _call number_ are use
 systems. 
 
 
-anchor:sip_19-20_item_status_update[]
+[#sip_19-20_item_status_update]
 
 ==== 19/20 Item Status Update ====
 
 
-anchor:sip_23-24_patron_status[]
+[#sip_23-24_patron_status]
 
 23/24 Patron Status 
 ^^^^^^^^^^^^^^^^^^^
@@ -539,7 +539,7 @@ These limitations are reflected in the 14-character _patron status_ string immed
 field definitions in your copy of the spec. 
 
 
-anchor:sip_25-26_patron_enable[]
+[#sip_25-26_patron_enable]
 
 25/26 Patron Enable 
 ^^^^^^^^^^^^^^^^^^^
@@ -547,7 +547,7 @@ anchor:sip_25-26_patron_enable[]
 Not yet supported. 
 
 
-anchor:sip_29-30_renew[]
+[#sip_29-30_renew]
 
 ==== 29/30 Renew ====
 
@@ -555,7 +555,7 @@ Evergreen supports the Renew message. Evergreen checks whether a penalty is spec
 renewals before blocking any SIP renewal.
 
 
-anchor:sip_35-36_end_session[]
+[#sip_35-36_end_session]
 
 ==== 35/36 End Session ====
 
@@ -568,7 +568,7 @@ in this context, and for evergreen it is hardcoded _Y_.
 
 
 
-anchor:sip_37-38_fee_paid[]
+[#sip_37-38_fee_paid]
 
 37/38 Fee Paid 
 ^^^^^^^^^^^^^^
@@ -576,7 +576,7 @@ anchor:sip_37-38_fee_paid[]
 Evergreen supports the Fee Paid message.
 
 
-anchor:sip_63-64_patron_information[]
+[#sip_63-64_patron_information]
 
 63/64 Patron Information 
 ^^^^^^^^^^^^^^^^^^^^^^^^
@@ -601,14 +601,14 @@ See <<sip_23-24_patron_status, 23/24 Patron Status>> for info on +BL+ and +CQ+ f
 
 
 
-anchor:sip_65-66_renew_all[]
+[#sip_65-66_renew_all]
 
 ==== 65/66 Renew All ====
 
 Evergreen supports the Renew All message.
 
 
-anchor:sip_93-94_login[]
+[#sip_93-94_login]
 
 93/94 Login 
 ^^^^^^^^^^^
@@ -629,12 +629,12 @@ _941_ means successful terminal login. _940_ or getting dropped means failure.
 When using a version of SIPServer that supports the feature, the Location (CP) field of the Login (93) message will be used as the workstation name if supplied. Blank or missing location fields will be ignored. This allows users or reports to determine which selfcheck performed a circulation.
 
 
-anchor:sip_97-96_resend[]
+[#sip_97-96_resend]
 
 ==== 97/96 Resend ====
 
 
-anchor:sip_99-98_sc_and_acs_status[]
+[#sip_99-98_sc_and_acs_status]
 
 ==== 99/98 SC and ACS Status ====
 
@@ -672,7 +672,7 @@ The Supported Messages field +BX+ appears only in +SIP2+, and specifies whether
 supported by the +ACS+ or not. 
 
 
-anchor:fields[]
+[#fields]
 
 ==== Fields ====
 

diff --git a/docs-antora/modules/admin/pages/web_client-login.adoc b/docs-antora/modules/admin/pages/web_client-login.adoc
index 529e251..91a6959 100644 (file)
--- a/docs-antora/modules/admin/pages/web_client-login.adoc
+++ b/docs-antora/modules/admin/pages/web_client-login.adoc
@@ -2,7 +2,7 @@ Logging into Evergreen
 -----------------------
 
 === Registering a Workstation ===
-anchor:register_workstation[]
+[#register_workstation]
 indexterm:[staff client, registering a workstation]
 
 Before logging into Evergreen, you must first register a workstation from your

diff --git a/docs-antora/modules/development/pages/support_scripts.adoc b/docs-antora/modules/development/pages/support_scripts.adoc
index fbf1df5..5c23518 100644 (file)
--- a/docs-antora/modules/development/pages/support_scripts.adoc
+++ b/docs-antora/modules/development/pages/support_scripts.adoc
@@ -57,7 +57,7 @@ to more thorough documentation, if available.
    -- Uses the output of marc2bre.pl (or similar tools) to generate the SQL
       for importing records into Evergreen in a parallel fashion
 
-anchor:_authority_control_fields[]
+[#_authority_control_fields]
 
 === authority_control_fields: Connecting Bibliographic and Authority records ===
 
@@ -95,7 +95,7 @@ Here is how the matching works:
 |=========================================================
 
 
-anchor:_marc_export[]
+[#_marc_export]
 
 === marc_export: Exporting Bibliographic Records into MARC files ===
 
@@ -215,7 +215,7 @@ best way to use this option is in combination with the `--items` and one of the
 `--library` or `--descendants` options to export *all* of a library's
 holdings both physical and electronic.
 
-anchor:_pingest_pl[]
+[#_pingest_pl]
 
 === Parallel Ingest with pingest.pl ===
 

diff --git a/docs-antora/modules/opac/pages/my_account.adoc b/docs-antora/modules/opac/pages/my_account.adoc
index 64446d5..fdad57a 100644 (file)
--- a/docs-antora/modules/opac/pages/my_account.adoc
+++ b/docs-antora/modules/opac/pages/my_account.adoc
@@ -1,5 +1,5 @@
 
-anchor:my_account[]
+[#my_account]
 
 
 === My Account ===
@@ -66,7 +66,7 @@ click _Search_!
 If using a public computer be sure to log out! 
 =================
 
-anchor:password_reset[]
+[#password_reset]
 
 ==== Password Reset ====
 

diff --git a/docs-antora/modules/opac/pages/using_the_public_access_catalog.adoc b/docs-antora/modules/opac/pages/using_the_public_access_catalog.adoc
index 30990cc..78f97a2 100644 (file)
--- a/docs-antora/modules/opac/pages/using_the_public_access_catalog.adoc
+++ b/docs-antora/modules/opac/pages/using_the_public_access_catalog.adoc
@@ -183,7 +183,7 @@ image::media/searchfilters2.PNG[search results with search filter enhancements]
 Each filter can be removed by clicking the X next to the filter name to modify the search within the search results screen.  Below the search box on the search results screen, there is also a link to _Refine My Original Search_, which will bring the user back to the advanced search screen where the original search parameters selected can be viewed and modified.
 
 
-anchor:numeric_search[]
+[#numeric_search]
 indexterm:[advanced search, numeric search]
 
 ==== Numeric Search ====
@@ -319,7 +319,7 @@ truncate any number of characters.
 
 === Search Methodology ===
 
-anchor:stemming[]
+[#stemming]
 
 Stemming 
 ^^^^^^^^
@@ -349,7 +349,7 @@ therefore the stemming algorithm does not recognize _gold_ as a stem of
 _golden_. 
 
 
-anchor:order_of_results[]
+[#order_of_results]
 
 ==== Order of Results ====