MARCXML extractor - Revision history

Akivela: /* Conversion details */

2011-06-15T07:49:28Z

‎Conversion details

Akivela at 07:47, 15 June 2011

2011-06-15T07:47:15Z

Akivela: /* Additional notes */

2011-01-20T20:19:13Z

‎Additional notes

Akivela: /* Additional notes */

2011-01-20T20:18:56Z

‎Additional notes

Akivela: /* Conversion details */

2011-01-20T20:17:25Z

‎Conversion details

Akivela: /* Conversion details */

2011-01-20T20:17:10Z

‎Conversion details

Akivela at 07:32, 19 August 2010

2010-08-19T07:32:03Z

Akivela: /* Additional notes */

2010-07-27T10:57:07Z

‎Additional notes

Akivela: /* Use example */

2010-07-27T10:55:52Z

‎Use example

Akivela: /* Additional notes */

2010-07-27T10:54:01Z

‎Additional notes

@@ Line 99: / Line 99: @@
 MARCXML to Topic Maps conversion creates a topic for each '''record''' entity found in MARCXML file. One association is created for each '''field''' in the record. Association type is based on a field code. Created record topic is added to the association as first player with static role '''Record (MARC)'''. For each subfield in the field, a topic is created for both subfield code and subfield value. The subfield value is the actual text content within the subfield entity. Both the subfield code topic and the subfield value topic are added to the association as a single member, i.e. a player-role pair, where the subfield code topic is a role and the subfield value topic is a player.
-As an exception, fields 001-009 and their content are added to the record topic as occurrences where occurrence types reflect field's code and occurrence data is the content of the field entity.
+As an exception, MARC fields 001-009 and their content are added to the record topic as occurrences where occurrence types reflect field's code and occurrence data is the content of the field entity.
 Subject identifier of the record topic is random if Wandora user has not specified matching SI pattern. If matching SI pattern is available, a resulting string is added to the record topic as a subject identifier.
@@ Line 105: / Line 105: @@
 By default record topic has no base name. If user has specified matching base name pattern, resulting string is added to the record topic as a base name.
-Record topics are instances of topic '''Record (MARC)'''.
+Record topics are made instances of topic '''Record (MARC)'''.
 == Additional notes ==

← Older revision		Revision as of 07:47, 15 June 2011
Line 1:		Line 1:
−	[http://www.loc.gov/standards/marcxml/ MARCXML] is a file format used to transfer and store ~~library data~~. MARCXML standard is developed by The Library of Congress' Network Development and MARC Standards Office. Wandora's MARCXML extractor converts MARCXML files to topic maps. Extractor starts with menu option '''File > Extract > Bibliographical > MARCXML extractor...'''. Wandora user can configure the conversion as described below.	+	[http://www.loc.gov/standards/marcxml/ MARCXML] is a file format used to transfer and store bibliographical information. MARCXML standard is developed by The Library of Congress' Network Development and MARC Standards Office. Wandora's MARCXML extractor converts MARCXML files to topic maps. Extractor starts with menu option '''File > Extract > Bibliographical > MARCXML extractor...'''. Wandora user can configure the conversion as described below.

	Wandora features also a batch conversion for MARCXMLs. Batch conversion tool is started with menu option '''File > Extract > Bibliographical > MARCXML batch extractor...'''. Batch extractor stores all converted topic maps in XTM format to '''wandora_export''' folder beside the MARCXML files.		Wandora features also a batch conversion for MARCXMLs. Batch conversion tool is started with menu option '''File > Extract > Bibliographical > MARCXML batch extractor...'''. Batch extractor stores all converted topic maps in XTM format to '''wandora_export''' folder beside the MARCXML files.

@@ Line 111: / Line 111: @@
 * User should note that the conversion schema respects MARCXML format. Conversion tries not to hide original file format but uses it's fields and subfields in the topic map.
 * Conversion tries to be non-lossy. It should be possible to convert extracted topic map back to MARCXML format.
-* There is a lot of semi-structured text in field contents. General principle is ''If you don't know what it means, leave it alone''. Conversion leaves this text intact.
+* There is a lot of semi-structured text in field contents. General principle is ''If you don't know what it means, leave it alone''. Conversion leaves the text intact.

@@ Line 109: / Line 109: @@
 == Additional notes ==
-* User should note that the conversion schema respects MARCXML format. Conversion tries not to hide original file format but uses it's fields and subfields as such in the topic map.
+* User should note that the conversion schema respects MARCXML format. Conversion tries not to hide original file format but uses it's fields and subfields in the topic map.
-* Conversion tries to be non-lossy. It should be possible to map converted topic map back to MARCXML format.
+* Conversion tries to be non-lossy. It should be possible to convert extracted topic map back to MARCXML format.
-* There is a lot of semi-structured text in field contents. Conversion leaves this text intact. General principle is ''If you don't know what it means, leave it alone''. However, this may change in future releases as it is possible to do some code to text mapping reliably.
+* There is a lot of semi-structured text in field contents. General principle is ''If you don't know what it means, leave it alone''. Conversion leaves this text intact.

@@ Line 103: / Line 103: @@
 Subject identifier of the record topic is random if Wandora user has not specified matching SI pattern. If matching SI pattern is available, a resulting string is added to the record topic as a subject identifier.
-By default record topic has no base name. If user has specified a matching base name pattern, resulting string is added to the record topic as a base name.
+By default record topic has no base name. If user has specified matching base name pattern, resulting string is added to the record topic as a base name.
 Record topics are instances of topic '''Record (MARC)'''.

@@ Line 97: / Line 97: @@
 == Conversion details ==
-MARCXML to Topic Maps conversion creates a topic for each '''record''' entity found in MARCXML file. One association is created for each '''field''' in record. Association type is based on field code. Created record topic is added to the association as a first player with static role '''Record (MARC)'''. For each subfield in field, a topic is created for both subfield code and subfield value. Subfield value is the actual text content within the subfied entity. Both subfield code topic and subfield value topic are added to the association as a single member, where subfield code topic is a role and subfield value topic is a player.
+MARCXML to Topic Maps conversion creates a topic for each '''record''' entity found in MARCXML file. One association is created for each '''field''' in the record. Association type is based on a field code. Created record topic is added to the association as first player with static role '''Record (MARC)'''. For each subfield in the field, a topic is created for both subfield code and subfield value. The subfield value is the actual text content within the subfield entity. Both the subfield code topic and the subfield value topic are added to the association as a single member, i.e. a player-role pair, where the subfield code topic is a role and the subfield value topic is a player.
-As an exception, fields 001-009 and their content is added to the record topic as an occurrence where occurrence type reflects field code and occurrence data is the content of field entity.
+As an exception, fields 001-009 and their content are added to the record topic as occurrences where occurrence types reflect field's code and occurrence data is the content of the field entity.
-Subject identifier of a record topic is random if user has not specified a matching SI pattern. If matching SI pattern is available,  resulting string is added to the record topic as a subject identifier.
+Subject identifier of the record topic is random if Wandora user has not specified matching SI pattern. If matching SI pattern is available, a resulting string is added to the record topic as a subject identifier.
 By default record topic has no base name. If user has specified a matching base name pattern, resulting string is added to the record topic as a base name.

← Older revision		Revision as of 07:32, 19 August 2010
Line 1:		Line 1:
−	~~'''NOTE: MARCXML extractor is not yet available in public Wandora distribution package.'''~~
−
	[http://www.loc.gov/standards/marcxml/ MARCXML] is a file format used to transfer and store library data. MARCXML standard is developed by The Library of Congress' Network Development and MARC Standards Office. Wandora's MARCXML extractor converts MARCXML files to topic maps. Extractor starts with menu option '''File > Extract > Bibliographical > MARCXML extractor...'''. Wandora user can configure the conversion as described below.		[http://www.loc.gov/standards/marcxml/ MARCXML] is a file format used to transfer and store library data. MARCXML standard is developed by The Library of Congress' Network Development and MARC Standards Office. Wandora's MARCXML extractor converts MARCXML files to topic maps. Extractor starts with menu option '''File > Extract > Bibliographical > MARCXML extractor...'''. Wandora user can configure the conversion as described below.

← Older revision		Revision as of 10:55, 27 July 2010
Line 13:		Line 13:


−	Wandora opens up a dialog. User selects '''~~Url~~''' tab and enters url ''http://www.loc.gov/standards/marcxml/xml/collection.xml'' to the text area. Then user clicks '''Extract''' button.	+	Wandora opens up a dialog. User selects '''Urls''' tab and enters url http://www.loc.gov/standards/marcxml/xml/collection.xml to the text area. Then user clicks '''Extract''' button.

← Older revision		Revision as of 10:54, 27 July 2010
Line 113:		Line 113:
	* User should note that the conversion schema respects MARCXML format. Conversion tries not to hide original file format but uses it's fields and subfields as such in the topic map.		* User should note that the conversion schema respects MARCXML format. Conversion tries not to hide original file format but uses it's fields and subfields as such in the topic map.
	* Conversion tries to be non-lossy. It should be possible to map converted topic map back to MARCXML format.		* Conversion tries to be non-lossy. It should be possible to map converted topic map back to MARCXML format.
		+	* There is a lot of semi-structured text in field contents. Conversion leaves this text intact. General principle is: If you don't know what it means, leave it alone. However, this may change in future releases as it is possible to do some code to text mapping reliably.