ulsdevteam/almaprisminvoice

A transform to take Alma invoices and create a Prism flat file

almaprisminvoice's Issues

Use Vendor Code and Invoice ID as Description

almaPrismInvoice/almaPrism.xslt

Lines 87 to 95 in e4b5abc

	<!-- TODO: was Voyager "vendor code" + " " + "voucher id", what should this be now? -->
	<xsl:call-template name="fixlenstring">
	<xsl:with-param name="pLength">32</xsl:with-param>
	<xsl:with-param name="pString">
	<xsl:value-of select="../../../../inv:vendor_code" />
	<xsl:text> </xsl:text>
	<xsl:value-of select="../../../../inv:unique_identifier" />
	</xsl:with-param>
	</xsl:call-template>

Set the PRISM Description as the Vendor Code and unique identifier for the Alma Invoice.

Change Vendor Additional Code to second component of Vendor FinSys Code

almaPrismInvoice/almaPrism.xslt

Lines 38 to 44 in e4b5abc

	<!-- 8 - 22, Vendor Site Code -->
	<xsl:call-template name="fixlenstring">
	<xsl:with-param name="pLength">15</xsl:with-param>
	<xsl:with-param name="pString">
	<xsl:value-of select="../../../../inv:vendor_additional_code" />
	</xsl:with-param>
	</xsl:call-template>

Instead of mapping the Vendor Additional Code to the PRISM Site Code, use the second component of the Vendor FinSys Code (after the pipe).

Map Alma Ledger Name to PRISM Source

almaPrismInvoice/almaPrism.xslt

Lines 108 to 114 in e4b5abc

	<!-- TODO: Convert Ledger Name into "ULS Library", "HSLS Library", "Law Library" -->
	<xsl:call-template name="fixlenstring">
	<xsl:with-param name="pLength">32</xsl:with-param>
	<xsl:with-param name="pString">
	<xsl:value-of select="inv:ledger_name" />
	</xsl:with-param>
	</xsl:call-template>

Map all values of Alma Ledgers (by prefix of naming convention) to the PRISM source values of:

• ULS Library
• HSLS Library
• Law Library

Confirm mapping of Invoice Line Type

almaPrismInvoice/almaPrism.xslt

Lines 77 to 80 in e4b5abc

	<!-- TODO: MISC (Processing?), TAX (?) -->
	<xsl:when test="../../inv:line-type[text() = 'SHIPMENT']">FREIGHT</xsl:when>
	<!-- TODO: verify if this is a safe assumption, or if we should enumerate each inv:line-type -->
	<xsl:otherwise>ITEM</xsl:otherwise>

FIS instructs to only use ITEM or FREIGHT for import. We need to confirm the mapping of possible Alma line types to these two PRISM line types.