Well, it’s done. The handout and slides as presented are posted here, and I’ll add them to our portal integration page (yeah, they’re sort of connected) when I return to Plymouth. The slides don’t stand on their own, but for those that were there, they should be helpful reminders of what was said what links we looked at.

One of the attendees took me to task for recommending MARC XML as the replacement for III’s proprietary schema, saying that it fails to leverage the full value of XML. He had a point, and I really should have been advocating for improvement without prejudicing what the result should be. MARC XML would be a step in the right direction, but it has its limitations. I was glad to see the interest, and my hopes for a solution are a lot higher now than they were before the show.

If nothing else, I’d recommend a schema that follows the generic recommendations for implementing Dublin Core in XML. Here are the important bits, minus the DC-specifics:

• A simple DC record is made up of one or more properties and their associated values.
• Each property is an attribute of the resource being described.
• Properties may be repeated.
• Each value is a literal string.
• Each literal string value may have an associated language (e.g. en-GB).

Here’s the big one, and it’s where III’s schema fails:

…Encode properties as XML elements and values as the content of those elements. For example:

<dc:title>Dublin Core in XML</dc:title>

To provide the counter example, here’s how the title field is represented in III’s schema:

	<VARFLD>
		<HEADER>
			<TAG>t</TAG>
			<NAME>TITLE</NAME>
			<LABEL>Title</LABEL>
			<SEQUENCENUM>0</SEQUENCENUM>
		</HEADER>
		<DisplayForm>Kitten's first full moon / Kevin Henkes</DisplayForm>
		<RTL>0</RTL>
		<MARCINFO>
			<MARCTAG>245</MARCTAG>
			<INDICATOR1>1</INDICATOR1>
			<INDICATOR2>0</INDICATOR2>
		</MARCINFO>
		<MARCSUBFLD>
			<SUBFIELDINDICATOR>a</SUBFIELDINDICATOR>
			<SUBFIELDDATA>Kitten's first full moon /</SUBFIELDDATA>
		</MARCSUBFLD>
		<MARCSUBFLD>
			<SUBFIELDINDICATOR>c</SUBFIELDINDICATOR>
			<SUBFIELDDATA>Kevin Henkes</SUBFIELDDATA>
		</MARCSUBFLD>
	</VARFLD>

There’s a lot of data there, but the structure is just strange.

Then, in one of those “duh” moments, I was reminded that I could purchase another index and ask III to index acq or cat date, thus solving the problem I now face in searching and limiting by those dates. Good point.

I was also reminded that I didn’t mention that the interface is neither REST nor SOAP. I did explain that the search URL syntax is different from the WebOPAC URL syntax, even though they could be the same (or, at least, more similar).

XML Server holds a lot of promise, but it needs development attention from III to be truly useful. Then, I’d also like to see III adopt a Web Services strategy that includes the OPAC, patron data, billing/fines/notices, and everything else.

Posted May 3, 2005 by Casey Bisson
Categories: Libraries & Networked Information. .

2 Comments

Comments RSS TrackBack Identifier URI

Leave a comment

Name (required)

Mail (will not be published) (required)

Website

 

User contributed tags for this post:

sex tv com (2844) - sex 300 (2750) - sex 300 com (1523) - sex tv (1361) - tv sex com (576) - sex com (345) - sexy tv (329) - sexy tv com (317) - rtl sex (316) - 300 COM (294) - sex sex sex com (222) - sex sex com (211) - www sex 300 com (190) - tv sex (176) - sex sex (164) - rtl tv com (134) - sex tv it (108) - sexy web com (105) - 300 sex (94) - 300 sex com (84) - sexy 300 (80) - sexy world com (77) - rtlsex (76) - rtl sex tv (74) - sex on tv com (71) - sex com 300 (69) - sexsex com (67) - sexy 300 com (59) - sex t v (53) - sexs 300 (51) - WWW SEX 300 (51) - sex web com (51) - sex 5 (50) - 300 (49) - photo sex com (47) - com sex (46) - www rtl tv com (44) - WWW SEX TV COM (42) - sexy 20tv (42) - sex (42) - sex web (39) - www.300.sex.com (38) - rtl tv sex (37) - sex tv key (36) - sex 20300 com (35) - WWW SEX TV (35) - sex world com (34) - rtl tvsex (34) - sex sex sex (34) - sexs server (34) - SEXY SEX 123 (33) - sex300com (32) - all (32) - rtl sexs (31) - sexsex (30) - sex tv 66 (29) - sexy 20tv com (29) - sex show (28) - sex 300 com sex 300 com (28) - WWWSEX 300 COM (25) - sex tv now (25) - cache 4dzo1lMaRVsJ s bestsupercars com r04 sex 300 com  (24) - sexs tv 2006 (24) - sexy tv it (23) - blog tv sex (22) - sex show v deo (22) - tv sexy (22) - WWW SEXY TV COM (21) - photo (21) - xml server (21) - sex improvement com (20) - WWW SEX COM (19) - sex and sex com (19) - sexy (19) - rtl tv (18) - sex dublin (18) - WWW SEX WEB COM (17) - www rtl tv (17) - sex shwo TV com (17) - www.rtl.de (16) - s e x com (16) - sex 20tv com (15) - sexy sex (15) - WWW 300 COM (15) - www.rtl.tv.com (13) - sex rtl (12) - www.RTL.tv (11) - sex com tv (11) - rtl.sex.tv (11) - tv 20sex com (11) - WWW TV SEX COM (11) - 3311183922622 (10) - www.300.com (10) - should (10) - sexy sex com (9) - sex video tv com (9) - WWW COM SEX (9) - tv sexs (9) - xml server iii (9) - TV SEXY COM (8) - time passing quote (8) - iii xml server (8) - WWW SEXY TV (8) - RTL TV SEXS (8) - rtl sexs tv (8) - com sex 300 (8) - WWWSEX TV (8) - tv earth com (7) - t v sex com (7) - tv world com (7) - rtl sex com (7) - sex shwo photo (7) - www.rtltv (7) - google erth server (7) - RTL SEKX (7) - WWWSEX 300 (7) - rtl sex movies (7) - WWW 300 SEX COM (7) - SEXsex TV (6) - WWWSEX SEX SEX COM (6) - WWW SEX sex (6) - sexsex.tv (6) - XML server applications (6) - WWW SEX SEX SEX COM (6) - cache R68Qihhb3usJ jamasp com q asp q sex tv com s 11 e (5) - RTL de sex (5) - web tv sex (5) - WWW 300 SEX (5) - WWW SEX COM 300 (5) - WWW SEX 20TV COM (5) - sexcom (5) - s x 300 com (5) - server sex (5) - WWW SEX TV IT (5) - sex.rtl (5) - 300.sex.com (5) - www sex300com (5) - WWW 300 (4) - sexs.videosu (4) - WWW SEXSEX COM (4) - rtl sexs videosu (4) - WWW sex TV DE (4) - tv sex tv (4) - RTL SEX T V (4) - 89 tvsex (4) - tv sex 300 (4) - www sex rtl (4) - w w w sex sex com (4) - r t l sex tv (4) - 2799051484749 (4) -