DLC-MODS Workbook 1.2

Pinky says, “Hello.”

Presented by University of Tennessee Libraries Digital Library CenterMelanie Feltner-Reichert, Metadata LibrarianChristine Haygood Deane, Software Developer

DLC-MODS Workbook 1.2When you first load the Workbook, 2 prompt messages appear that you fill in. Then a Welcome alert appears, and the workbook is fully loaded.

DLC-MODS Workbook 1.2

Now the Workbook is fully loaded in non-debug mode.

DLC-MODS Workbook 1.2This is the Welcome Page in debug mode. Note that the Upper (yellow) and Lower (pink) Frames show, along with the Display Frame (grey).

DLC-MODS Workbook 1.2The reason for the prompts and alert at the beginning is to allow the Lower (pink) Frame to fully load. This frame holds functions and arrays. Once loaded, these functions are never

loaded again and are available to all pages. This saves time for the user.

DLC-MODS Workbook 1.2The Left Frame contains the active page link display. The link to the current page in the

Display Frame is highlighted so you know where you are. For debug purposes, there is a link to the static link page so you can navigate to all places.

DLC-MODS Workbook 1.2The information you enter into the prompts is loaded to input boxes on the header page. You

must enter your XML filename on the input box on the <header> page and click Save.

DLC-MODS Workbook 1.2When you click the Save button, an alert appears prompting you to check

your filename. After you click OK, the data is saved.

DLC-MODS Workbook 1.2This is the display of your saved data in XML format. Note the Name, Institution, and

FILENAME values. You may go back to the <header> page to revise the data.

DLC-MODS Workbook 1.2If you visit the Upper Frame, you can see where the data is really saved. All input

form variables from all input pages are saved to the Upper Frame.

DLC-MODS Workbook 1.2Returning to the <header> input page, scroll to the bottom. This display shows the array of DOM elements on the page. Every element except buttons is saved to the Upper Frame.

DLC-MODS Workbook 1.2Moving to the <titleInfo> input page, note the Summary of Requirements at the top of the

page. This is to help the user decide what is important for creating a MODS record.

DLC-MODS Workbook 1.2These are the input boxes on the <titleInfo> page. Note the Add/Remove

buttons. This allows creation of more than one titleInfo block.

DLC-MODS Workbook 1.2When you click Save, the generated XML tags are displayed, with your inputs in red. If you had used the Add titleInfo block option, multiple sets of <mods:titleInfo>…</mods:titleInfo>

tags would have been generated.

DLC-MODS Workbook 1.2Scrolling to the bottom of the <titleInfo> page you see the elements array. Note sentinel

elements. This allows dynamic page loading so that you can have more than one title block for the digital object. Again, all input pages work the same, saving to the Upper Frame.

DLC-MODS Workbook 1.2This shows how <titleInfo> form values are saved. The elements array is turned into a string that is saved to ti_block_list. The ti_block_list is a hidden variable in the Display Frame and a

textarea in the Upper Frame. The separator is parent.U.split_token ( @@@@@ ).

DLC-MODS Workbook 1.2When you return to the <titleInfo> page at any time during the session, the values from ti_block_list string in

the Upper Frame are loaded into the <titleInfo> page input box array. This is how the data is persisted for the duration of a session. And this is how it works for all pages, including Reload.

DLC-MODS Workbook 1.2This is the Reload Dev page, which is exactly the same as the simple Reload page except for a few extra buttons. The Load Test File button allows you to load a hard-coded xml input file

that I created for testing, the fictional biography of Fenway Thigpen.

DLC-MODS Workbook 1.2Clicking the Load Test File button causes the xml to be loaded. When you click

Process Data in TextArea, this will parse the data and load it to the Upper Frame.

DLC-MODS Workbook 1.2The display of this alert is proof that reloading completed successfully.

Data has been parsed and saved to the upper frame.

DLC-MODS Workbook 1.2What happens when you click the Process button on the reload page? First the xml tags are

broken up into element blocks. These are loaded to the Upper Frame in the U2 form in textareas. Each textarea corresponds to one input page. Then each textarea is processed…

DLC-MODS Workbook 1.2…and loaded into corresponding Upper Frame form UF inputs. <header> inputs are slightly different from

other pages, but the <titleInfo> ti_block_list text area is a good representative of all the others. Note the string of values separated by @@@@@ tokens. These values are ready to load in the <titleInfo> page.

DLC-MODS Workbook 1.2This shows the <titleInfo> values from Reload. These values came from the ti_block_list textarea in the Upper Frame. You can use the Load Test File to explore how pages work.

DLC-MODS Workbook 1.2You can also look at your values on the Review Page. Below are some <titleInfo> values

from Reload on Fenway Thigpen. You can scroll down and see all values from Reload. If you have on an incomplete file, the Review Page is a quick way to find out what is left to be done.

DLC-MODS Workbook 1.2The Review Page provides a table that displays BLOCK ITERATION and PAGE VALIDATION for all pages in the Workbook. These comments are generated at the top of each XML file created by the workbook and are designed specifically to help with Reload. See how <titleInfo> has BI=2, which causes 2 <titleInfo> blocks.

DLC-MODS Workbook 1.2Cutting to the Chase. You have filled out your inputs and saved them,

now it is time to go to the Final Page and create an XML file.

DLC-MODS Workbook 1.2Scroll down on the Final Page to the buttons. You should probably click

View MODS TAGS first to look at your work.

DLC-MODS Workbook 1.2After you click on View MODS TAGS, the display of the entire XML file will appear, with input values in red.

You will have to scroll down to see the entire XML output. If you have problems using other download buttons, you can always cut and paste this display into notepad to create your final XML file.

DLC-MODS Workbook 1.2The Create Incomplete button is for saving work in progress. The Create Final

button is for finished work. Clicking either one should bring up a download dialog.

DLC-MODS Workbook 1.2Clicking Create Incomplete or Create Final will bring up the download dialog for your browser.

Go through standard steps for your browser and save your file to the correct directory.

DLC-MODS Workbook 1.2

Your xml output should look like this.

DLC-MODS Workbook 1.2In this release of the Workbook, php is needed to create the download. If

you do not have php, click on the Display XML as HTML button.

DLC-MODS Workbook 1.2When you click the Display XML as HTML button, you will see the alert shown below. When you close the alert, the HTML page will appear.

DLC-MODS Workbook 1.2The Display Frame contains the XML as HTML. Right Click on the

display frame for the browser menu containing View Source to show up.

DLC-MODS Workbook 1.2

Clicking on View Source should create your xml file as a .txt file.

DLC-MODS Workbook 1.2This is the text file created by View Source from the Display Frame. You will have to edit out the lines before the <?xml line and you will have to change the filename to the correct name

with the .xml file extension, then you will have a final MODS record.

DLC-MODS Workbook 1.2The Workbook contains User Documentation that is aimed at the standard user

( probably a cataloger ) with brief notes about each input page.

DLC-MODS Workbook 1.2The Workbook contains Programmer Documentation, with technical

notes to help in customizing the code.

DLC-MODS Workbook 1.2

Pinky says, “Good-bye.”

Code available online at: http://dlc.lib.utk.edu/~cdeane/UTK_LIB_DLC/beta.htmAnd available as download at: http://dlc.lib.utk.edu/~cdeane/UTK_LIB_DLC/beta_download.htm