source: trunk/gli/help/help.html@ 6075

Last change on this file since 6075 was 5472, checked in by mdewsnip, 21 years ago

HTML file containing all the help text. Generated by applying the gen-one-html.xsl transform to help.xml, using ApplyXSLT.class.

  • Property svn:keywords set to Author Date Id Revision
File size: 62.9 KB
Line 
1<html>
2<head>
3<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
4<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
5<title>The Greenstone Librarian Interface - Help Pages</title>
6</head>
7<body bgcolor="#E0F0E0">
8<a name="introduction">
9<h1>Section 1: Introduction</h1>
10</a>
11
12The Greenstone Librarian Interface is a tool for collecting and marking up documents, then building digital library collections. It provides access to the Greenstone Digital Library Software's functionality from a graphical point and click interface.
13
14
15 <a name="ofmiceandmenus">
16<h3>Section 1.1: Of Mice and Menus</h3>
17</a>
18
19This section provides basic information about interacting with the Librarian Interface.
20If you are familiar with programs such as Internet Explorer or Microsoft
21Office and are comfortable with mouse clicks and menus, skip to the <a href="#howtoavoidthisdocument">next section</a>.
22 <p></p>
23
24The Librarian Interface follows Microsoft Windows conventions and draws upon
25ordinary knowledge of Windows.
26<p></p>
27Any part of the screen that you interact with, such as a button or text field,
28is called a "control". At any given time one control, called the "focus", is
29highlighted and responds to the keyboard. Several controls allow you to select
30parts that are highlighted in dark blue. Some controls are greyed out to
31indicate that they are disabled.
32<p></p>
33You can move and left- or right-click the mouse in the usual way. Many
34components also allow you to "drag" them, by clicking and holding the left
35mouse button, move them with the mouse, and "drop" them elsewhere by releasing
36the button. Potential drop targets alter their appearance when a component
37hovers over them.
38<p></p>
39You can use the keyboard to type into text fields. Keyboard alternatives are
40available for many controls, indicated by a key name in square brackets -- for
41example, [Tab] alters the focus. The plus sign shows if other keys must be
42pressed at the same time.
43<p></p>
44Exit the Librarian Interface program by choosing "Exit" from the "File"
45menu. Your collection will be saved first.
46
47To access a menu, hold down [ALT] and press the corresponding letter
48(underlined). For example, for the "File" menu press [ALT] + [F]. To choose an
49item, press the corresponding key. For example, while in the File menu
50press [S] to "Save" a collection.
51 <a name="howtoavoidthisdocument">
52<h3>Section 1.2: How to Avoid Reading This Document</h3>
53</a>
54
55Don't read this help text all the way through! Just read enough to learn
56how to get help when you need it.
57 <p></p>
58
59The "Help" menu item marks what may be the most appropriate help item with a
60little book icon.
61<p></p>
62For many controls, if you station the mouse over them a
63"tool tip" appears that says what they do.
64<p></p>
65Before using the Librarian Interface, first read the Greenstone
66documentation.
67 <a name="startingoff">
68<h1>Section 2: Starting Off</h1>
69</a>
70
71This section covers how to create, save and load a collection.
72
73
74
75 <a name="creatingacollection">
76<h3>Section 2.1: Creating a New Collection</h3>
77</a>
78
79
80
81<p></p>
82
83To create a new collection, open the "File" menu and choose "New". Several
84fields need to be filled out -- but you can change their values later if you
85need to, in the design view.
86<p></p>
87"Title" is the text displayed at the top of your collection's home page. It can
88be any length.
89<p></p>
90"Short Name" is the collection's filename. It must be unique.
91<p></p>
92"Author's Email" should be a valid email address.
93<p></p>
94"Description of content"
95should describe, in as much detail as possible, what the collection is about.
96Use the [Enter] key to break it into paragraphs.
97<p></p>
98Finally you must specify whether the new collection will have the same
99appearance and metadata sets as an existing collection, or whether to start a
100default "New Collection".
101<p></p>
102Click "OK" to create the collection. If you chose "New Collection" you are
103prompted for the metadata sets to use in it. You can choose more than one, and
104you can add others later.
105<p></p>
106Clicking "Cancel" returns you to the main screen immediately.
107
108Buttons, like menus, have one character underlined. To "click" the button,
109press [ALT] and the underlined character at the same time.
110 <a name="savingacollection">
111<h3>Section 2.2: Saving the Collection</h3>
112</a>
113
114
115
116<p></p>
117
118Save your work regularly by opening the "File" menu and choosing "Save".
119Saving a collection is not the same as making it ready for use in Greenstone
120(see <a href="#producingthecollection">Producing Your Collection</a>).
121<p></p>
122The Librarian Interface protects your work by saving it whenever you exit the
123program or load another collection.
124
125Saved collections are written to a file named for the collection and with file
126extension ".col", located in a folder of the same name within your Greenstone
127installation's "collect" folder.
128 <a name="openingacollection">
129<h3>Section 2.3: Opening an Existing Collection</h3>
130</a>
131
132
133
134<p></p>
135
136To open an existing collection, choose "Open" from the "File" menu to get the
137Open Collection prompt. A list of your Greenstone collections appears.
138Select one to see its description, and click "Open" to load it. If you seek a
139collection that resides outside Greenstone's "collect" folder, click "Browse"
140for a file system browsing dialog.
141
142In case more than one Greenstone Librarian Interface program is running
143concurrently, the relevant directories are "locked" to prevent interference.
144On opening a collection, a small temporary lock file is created in its
145folder. Before opening a collection, the Librarian Interface checks to ensure
146that no lock file already exists. You can tell whether a collection is locked
147by the colour of its icon: green for a normal collection, red for a locked
148one. However, when the Librarian Interface is exited prematurely the lock file
149is sometimes left in place. When you open such a collection, the Librarian asks
150if you want to "steal" control of it. Never steal a collection that someone
151else is currently working on.
152 <a name="huntingforfiles">
153<h1>Section 3: Hunting For Your Files</h1>
154</a>
155
156The Librarian Interface can run in different configurations. This section only
157applies when the "hunt" and/or "mirror" views are enabled. If these tabs do
158not appear, advanced users can enable them by editing the "config.xml" file in
159the Librarian Interface installation folder (or, on a multiuser system, in your
160home directory's ".gli" folder) to set the values of "workflow.browse" and
161"workflow.mirror" to "true".
162<p></p>
163When using web resources, the Librarian Interface operates in two stages. This
164section describes the first, Hunting, where you browse the Internet for files
165of interest. The <a href="#downloadingfiles">next section</a> describes the second stage, Mirroring, where these files can be downloaded.
166
167 <a name="thehuntview">
168<h3>Section 3.1: The Hunt view</h3>
169</a>
170
171This section describes how to use the simplified browsing interface to locate resources on the Internet.
172 <p></p>
173
174The Hunt view is accessed by clicking on its tab. Most of the screen shows a
175web page. Hyperlinks work in the usual way. Underneath the page is a status bar
176that shows you what the browser is doing.
177<p></p>
178You type URL addresses into the address field above the page.
179<p></p>
180To the left and right of the address field are web browser buttons for Back,
181Reload, Home, Go, Stop and Forward.
182 <a name="downloadingfiles">
183<h1>Section 4: Downloading Chosen Files</h1>
184</a>
185
186To enable web mirroring see <a href="#huntingforfiles">Hunting For Your Files</a>.
187To download web pages you need to install the mirroring tool wget (version v1.8
188recommended) and make it accessible from the Librarian Interface "install"
189folder.
190<p></p>
191Once web resources, the second stage is to download (or "mirror") the
192files you need. This section explains the Librarian Interface's mirroring
193process.
194
195 <a name="themirrorview">
196<h3>Section 4.1: The Mirror view</h3>
197</a>
198
199This section describes how to configure a download task and control the downloading process.
200 <p></p>
201
202Access the "Mirror" view by clicking its tab. The top half of the screen shows the downloading controls. The bottom half is initially empty, but will show a list of pending downloading jobs if there are some.
203<p></p>
204Files are downloaded into a folder in the workspace tree called "Public
205WebCache" (only present when mirroring is enabled), and can be used in all
206collections built with the Librarian Interface. When a collection is open a
207second folder, "Private WebCache", appears, which only that collection can access files from. Files in both these areas are named by their full web
208URL. A new folder is created for each host, followed by others for each part
209of the path. This ensures that each file is distinct.
210<p></p>
211Use the first of the download configuration controls, "Source URL", to enter the URL of a
212target resource. If you have come from the "Hunt" view, this field points to
213the last page visited. Use the "Download Depth" control to determine how many
214 hyperlinks deep to go when downloading: 0 means follow no hyperlinks and grabs just the
215target resource. The depth limit is
216ignored when downloading media other than html pages. Use the "Destination Folder" radio
217button control to choose whether the files are cached into the shared public
218folder or the private collection-specific folder (if available). Next, there are four checkbox controls which can be set to turn on the specified feature for a specific download. A fifth checkbox control "Automatically remove failed downloads..." does not pertain to a specific download, but instead clears the list of any failed download information, and prevents any future failures from appearing in the list. The final control is a "Download" button, which adds to the download list a new job corresponding to the configuration
219settings.
220<p></p>
221The download list has an entry for each unfinished download. For each entry, a
222central region with several lines of text and a progress bar is flanked by two
223buttons. The text gives details of the task, and updates as the task
224progresses, while the bar measures progress. The "play" triangle on the left
225button starts the current task and then changes to a double vertical bar, which
226pauses the current download. The "stop" square on the right button removes the
227current download task from the list. Download tasks are removed from the list
228when they finish successfully (ones that fail are controlled by the "Automatically remove failed downloads..." checkbox).
229
230The <a href="#preferences">Preferences section</a> describes how to establish an Internet connection
231via a proxy. If authentication is needed, the proxy server prompts for
232identification and password. The Librarian Interface does not store passwords
233between sessions.
234 <a name="collectingfiles">
235<h1>Section 5: Collecting Files for Your Collection</h1>
236</a>
237
238Once you have a new collection you need to get some files into it. These may
239come from your ordinary file space, or from other Greenstone collections. Some
240may already have attached metadata. This section describes how to import files.
241
242
243
244
245
246 <a name="thegatherview">
247<h3>Section 5.1: The Gather View</h3>
248</a>
249
250This section introduces the Gather area that you use to select what files
251to include in the collection you are building.
252 <p></p>
253
254The Librarian Interface starts with the Gather view. To return to this view
255later, click the "Gather" tab directly below the menu bar.
256<p></p>
257The two large areas titled "Workspace" and "Collection" are used to move files
258into your collection. They contain "file trees", graphical structures that
259represent files and folders.
260<p></p>
261Select an item in the tree by clicking it. (There are other ways; see below.)
262Double-click a folder, or single-click the switch symbol beside it, to expand (or collapse)
263its contents. Double-click a file to open it using its associated application
264program (see <a href="#fileassociations">File Associations</a>).
265<p></p>
266The Workspace file tree shows the sources of data available to the Librarian
267Interface -- the local file system (including disk and CD-ROM drives), the
268contents of existing Greenstone collections, and the public and private
269download caches if Web mirroring is enabled. You can copy and view these files
270but you cannot move, delete, or edit them. Navigate this space to find the
271files you want to include in the collection.
272<p></p>
273The Collection file tree represents the contents of the collection so
274far. Initially, it is empty.
275<p></p>
276You can resize the spaces by mousing over the grey bar that separates the trees
277(the shape of the pointer changes) and dragging.
278<p></p>
279Beneath is the Status Area, which describes the state of the Librarian
280Interface: how many items are selected and what action is requested. It
281reports on the progress of actions that involve files, which can take some time
282to complete. The "Stop" button stops any action that is currently in progress.
283<p></p>
284Two large buttons occupy the lower right corner of the screen. "New Folder", with a picture
285of a folder, creates new folders (see <a href="#creatingfolders">Creating folders</a>).
286"Delete", with a garbage can, removes files. Clicking the Delete button will remove any selected files from the Collection file tree. Alternatively, files can be deleted by dragging them onto the Delete button.
287
288To select several sequential items, select the first and then hold down [Shift]
289and click on the last -- the selection will encompass all intervening
290items. Select non-sequential files by holding down [Ctrl] while clicking. Use
291these two methods together to select groups of non-adjacent items.
292<p></p>
293Certain folders -- such as the one containing your own web pages -- sometimes
294have special significance. The Librarian Interface can map such folders to
295the first level of the file tree. To do this, right-click the desired
296folder. Select "Map", and enter a name for the folder. To remove an item,
297right-click the mapped folder and select "Unmap Folder".
298 <a name="creatingfolders">
299<h3>Section 5.2: Creating Folders</h3>
300</a>
301
302
303
304<p></p>
305
306Use folders in the Collection file tree to group files together and make them
307easier to find. Folders can be placed inside folders. There is virtually no
308limit to how many folders you can have or how deeply they can be nested.
309<p></p>
310To create a new folder, optionally select an existing folder in the Collection
311Tree and click the New Folder button. The new folder appears within the
312selected one, or at the top level if none is selected. You are prompted for the
313folder's name (default "New Folder").
314<p></p>
315Folders can also be created by right-clicking over a folder, choosing "New
316Folder" and proceeding as above.
317 <a name="addingfiles">
318<h3>Section 5.3: Adding Files</h3>
319</a>
320
321
322
323<p></p>
324
325Files can be copied into the collection by dragging and dropping. The mouse
326pointer becomes a ghost of the selected item (or, if more than one is selected,
327the number of them). Drop the selection into the Collection Tree to copy the
328files there (if the source was the Workspace Tree) or move them around within
329the collection (if the source was the Collection Tree).
330<p></p>
331When copying multiple files, they are all placed in the target folder at the
332same level, irrespective of the folder structure they occupied originally.
333When you copy a second file with the same name into the same folder, you are
334asked whether to overwrite the first one. Respond "No" and the file will not be
335copied, but the others will be. To cancel all remaining copy actions, click the
336"stop" button.
337<p></p>
338Only the "highest" items in a selection are moved. A folder is higher than its
339children. You cannot select files within a folder and also the folder itself.
340
341When you add a file, the Librarian Interface searches through the source
342folders for auxiliary files containing metadata previously assigned to the
343added file and, if it finds one, begins to import this metadata. As the
344operation proceeds, you may be prompted (perhaps several times) for extra
345information to match the imported metadata to the metadata sets in your
346collection. This process involves many different prompts, described in the <a href="#importingpreviouslyassignedmetadata">Importing Previously Assigned Metadata</a> section. For a more detailed
347explanation of associating metadata with files read Chapter 2 of the Greenstone
348Developer's Guide -- Getting the most out of your documents.
349 <a name="removingfiles">
350<h3>Section 5.4: Removing Files</h3>
351</a>
352
353
354
355<p></p>
356
357There are several methods for removing files and folders. You must first
358indicate what items to remove by selecting one or more files and folders as
359described in <a href="#thegatherview">The Gather View</a>.
360<p></p>
361Once files have been selected, click the "delete" button to remove them, or
362press the [Delete] key on your keyboard, or drag them from the collection to
363the delete button and drop them there.
364 <a name="filteringthetree">
365<h3>Section 5.5: Filtering the Tree</h3>
366</a>
367
368"Filtering" the collection tree allows you to narrow down the search for particular files.
369 <p></p>
370
371The "Show Files" pull-down menu underneath each tree shows a list of predefined
372filters, such as "Images". Choosing this temporarily hides all other files in
373the tree. To restore the tree, change the filter back to "All Files". These
374operations do not alter the collection, nor do they affect the folders in the
375tree.
376
377You can specify a custom filter by typing in a pattern to match files against.
378Use standard file system abbreviations such as "*.*" or "*.doc" ("*" matches
379any characters).
380 <a name="enrichingacollection">
381<h1>Section 6: Enriching the Collection with Metadata</h1>
382</a>
383
384Having gathered several files into the collection, now enrich them with
385additional information called "metadata". This section explains how metadata is
386created, edited, assigned and retrieved, and how to use external metadata
387sources (also see Chapter 2 of the Greenstone Developer's Guide -- Getting the most
388out of your documents).
389
390
391
392
393
394
395
396
397 <a name="theenrichview">
398<h3>Section 6.1: The Enrich View</h3>
399</a>
400
401
402
403<p></p>
404
405Use the Enrich view to assign metadata to the documents in the collection.
406Metadata is data about data -- typically title, author, creation date, and so
407on. Each metadata item has two parts: "element" tells what kind of item it is
408(such as author), and "value" gives the value of that metadata element (such as
409the author's name).
410<p></p>
411On the left of the "Enrich" view is the Collection Tree. To the right is the Metadata Table, which shows metadata for any selected files or folders in the Collection Tree. Columns are named in
412grey at the top, and can be resized by dragging the separating line. Clicking
413any row transfers its details to the MetaEdit Controls below. If several files
414are selected, black text indicates that the value is common to all of the
415selected files, while grey text indicates that it is not. Black values may be
416updated or removed, while grey ones can be removed from those that have it, or
417appended to the others.
418<p></p>
419A folder icon may appear beside some metadata entries. This indicates that the
420values are inherited from a parent (or ancestor) folder. Inherited metadata
421cannot be edited or removed, only appended to or overwritten. Click on the
422folder icon to go immediately to the folder where the metadata is assigned.
423<p></p>
424The MetaEdit Controls at the lower right appear only when a file is selected
425from the tree and a row is selected from the table. Use them to update, append,
426and remove the metadata value. The value field is for entering or editing the
427metadata value. Beside it is a button labelled "..." which, when clicked,
428opens a larger editing box. In the buttons below, "Append" assigns the value as
429new metadata and adds it to any existing values for the selected element,
430"Replace" overwrites the selected existing value with the new one, and "Remove" clears
431the selected value. Underneath, labelled "All Previous Values", is the "Value
432Tree".
433<p></p>
434The Value Tree expands and collapses. Usually it is a list that shows all
435values entered previously for the selected element. Clicking an entry
436automatically places it into the value field. Conversely, typing in the text
437field selects the Value Tree entry that starts with the characters you have
438typed. Pressing [Enter] auto-completes the typing with the selected value.
439<p></p>
440Metadata values can be organised into a hierarchy. This is shown in the Value Tree using folders for internal levels. Hierarchical values can be entered using the character "\" to separate the levels. For
441example, "Cards\Red\Diamonds\Seven" might be used in a hierarchy that represents a pack of playing cards. This enables values to be grouped together. Groups can also be assigned as metadata to files.
442<p></p>
443Greenstone extracts metadata automatically from documents into a metadata set
444whose elements are prefixed by "ex.". This has no value tree and cannot be
445edited, so the edit controls are hidden if such an entry is selected. The
446"..." button still serves to expand the value, but the text cannot be edited.
447 <a name="selectingmetadatasets">
448<h3>Section 6.2: Selecting Metadata Sets</h3>
449</a>
450
451
452
453<p></p>
454
455Sets of predefined metadata elements are known as "metadata sets". An example
456is the Dublin Core metadata set. When you add a metadata set to your
457collection, its elements become available for selection. You can have more than
458one set; to prevent name clashes a short identifier that identifies the
459metadata set is pre-pended to the element name. For instance the Dublin Core
460element Creator becomes "dc.Creator". Metadata sets are stored in the
461Librarian Interface's metadata folder and have the suffix ".mds".
462<p></p>
463To add a metadata set, choose "Metadata Sets" from the menu bar and select the
464"Import Set" action. A list appears that shows the sets stored in the Librarian
465Interface's metadata folder. Choose one and open it, or click "Browse" to
466locate metadata set files stored elsewhere. If the metadata elements have associated value trees, you will be asked whether to import
467all values associated with the elements in the set, just those values that make
468up the structure of hierarchy-based metadata, or no values at all.
469
470To install a newer version of a metadata set, simply add it as above. The
471Librarian Interface merges the sets, but does not alter values you have
472entered. You may be asked how to merge certain elements. For example if the
473current set and the one you are importing share a common element (which is
474likely if you are installing a new version of a set), you are shown as much
475information about the existing and new elements as possible, and asked how to
476proceed. Options include merging the elements, renaming the new one, replacing
477the old element entirely, or skipping this element. When merging two elements
478you are confronted with the same options, but this time at the "attributes"
479(rather than "elements") level. You can cancel the import operation at any
480time.
481<p></p>
482The ".mds" files are expressed in XML format. You can edit an existing metadata
483set or create a new one with an ordinary text editor. If you are starting a
484new file, copy the Document Type Definition and be sure to follow it, otherwise
485the Librarian Interface will be unable to load the metadata set. Use of an
486XML validator or validating editor is recommended.
487<p></p>
488To export a metadata set, or part of one (e.g. its assigned value hierarchy, or
489all its values), return to the Librarian Interface and choose "Export Set" from
490the "Metadata Set" menu. You will be asked to select appropriate export
491options, and a file to export into.
492 <a name="appendingmetadata">
493<h3>Section 6.3: Appending New Metadata</h3>
494</a>
495
496
497
498<p></p>
499
500We now add a metadata item -- both element and value -- to a file. First select
501the file from the Collection file tree on the left. The action causes any
502metadata previously assigned to this file to appear in the table at the right.
503<p></p>
504Next select the metadata element you want to add by clicking its row in the
505table.
506<p></p>
507Type the value into the value field. Do not use the character "\", as it is
508used for constructing hierarchies. When finished, click "Append" to add the new
509value as metadata for the chosen file. The value immediately appears in the
510Metadata table.
511<p></p>
512You can also add metadata to a folder, or to several multiply selected files at
513once. It is added to all files within the folder or selection, and to child
514folders. Keep in mind that if you assign metadata to a folder, any new files in
515it automatically inherit the folder's values.
516<p></p>
517When you add metadata to multiple files at once, you will be prompted for confirmation for any files that already have a value for that metadata. You are shown the name of the file in question, the element's
518title, previously-assigned values for this element, and the new value. The
519buttons offer different options: "Append" appends the metadata to the file
520without altering any existing values; "Append All" adds the new value to all
521other files too, without requiring individual confirmation; "Skip File" proceeds to the next file; "Cancel"
522undoes any changes and cancels the action.
523<p></p>
524If you choose metadata that occurs in some of the selected files and click
525"Append", it is added to the other files in the selection too.
526
527You can add structure to metadata values by using paths as described in <a href="#theenrichview">The Enrich View</a>. Correct any mistakes in creating hierarchies by using
528the metadata set editor explained in <a href="#editingmetadatasets">Editing Metadata Sets</a>.
529 <a name="addingpreviouslydefinedmetadata">
530<h3>Section 6.4: Adding Previously Defined Metadata</h3>
531</a>
532
533
534
535<p></p>
536
537To add metadata that has an existing value, first select the file, then select
538the required value from the value tree, expanding hierarchy folders as
539necessary. The value of the selected entry automatically appears in the Value
540text field (alternatively, use the value tree's auto-select and auto-complete
541features). Click "Append" to add the metadata to the selected file.
542<p></p>
543The process of adding metadata with already-existing values to folders
544or multiple files is just the same.
545 <a name="updatingmetadata">
546<h3>Section 6.5: Updating Metadata</h3>
547</a>
548
549
550
551<p></p>
552
553To update the value of a piece of metadata, first choose the file to which that
554value applies, and then the metadata element whose value you want to change.
555Your selection appears in the metadata edit controls. Edit the value field and
556click "Replace" to alter the metadata.
557<p></p>
558The process is the same when updating a folder with child folders or multiple
559files, except that when you click "Replace" you are asked what to do with the
560other files. The buttons offer different options: "Replace" replaces any
561previous value with the new one; "Replace All" adds the new value in the same
562way to all other files; "Skip File" skips the current file and proceeds to the
563next; "Cancel" undoes any changes and cancels the action. You can only update
564metadata that is common to all files selected. For a folder, this means that
565all its contents must share the same metadata.
566<p></p>
567The value tree shows all previous values, not just those currently assigned.
568Thus the value you have replaced will remain in the value tree.
569 <a name="removingmetadata">
570<h3>Section 6.6: Removing Metadata</h3>
571</a>
572
573
574
575<p></p>
576
577You remove metadata the same way as you update it. First select a file from the
578file tree, then use the metadata table to select the metadata. If the metadata
579has a value assigned, the "Remove" button in the MetaEdit Controls becomes
580active. Click it to remove the metadata from the specified file. Other files
581remain unchanged, and the value remains in the Value Tree.
582<p></p>
583When you remove metadata from a folder, or from several files, you are
584presented with various options: removing the metadata from this file, removing
585it from this and all other files, and skipping this file. You can cancel the
586operation at any time. If you choose metadata that is not common to all the
587selected files and click "Remove", the metadata is removed from those
588files that have it; all others are unaffected.
589 <a name="reviewingmetadata">
590<h3>Section 6.7: Reviewing Assigned Metadata</h3>
591</a>
592
593
594
595<p></p>
596
597Sometimes you need to see the metadata assigned to many or all files at once -- for instance,
598to determine how many files are left to work on, or to get some idea of the
599spread of dates.
600<p></p>
601Select the files you wish to examine, and from the "Metadata Set" menu choose "Assigned Metadata...". A window called
602"All Metadata", dominated by a large table with many columns, appears. The
603first column shows file names; the rows show all metadata values assigned to
604those files.
605<p></p>
606Drawing the table can take some time if many files are selected. You can continue to use the Librarian
607Interface while the "All Metadata" window is open.
608<p></p>
609Click "Close" to hide the window.
610
611You can also view the "All Metadata" table by selecting the files you wish to
612examine, right-clicking, and choosing "Assigned Metadata...". If a folder has
613been selected, all its child files are included in the table.
614<p></p>
615When it gets too large, you can filter the "All Metadata" table by applying
616filters to the columns. As new filters are added, only those rows that match
617them remain visible. To set, modify or clear a filter, click on the "funnel"
618icon at the top of a column. You are prompted for information about the filter.
619Once a filter is set, the column header changes colour.
620<p></p>
621The prompt has a "Simple" and an "Advanced" tab. The Simple version filters
622columns so that they only show rows that contain a certain metadata value ("*"
623matches all values). You can select metadata values from the pull-down list.
624The Advanced version allows different matching operations: must start with,
625does not contain, alphabetically less than and is equal to. The value to be
626matched can be edited to be any string (including "*"), and you can choose
627whether the matching should be case insensitive. Finally, you can specify a
628second matching condition that you can use to specify a range of values (by
629selecting AND) or alternative values (by selecting OR). Below this area is a
630box that allows you to change the sort order (ascending or descending). Once
631you have finished, click "Set Filter" to apply the new filter to the column.
632Click "Clear Filter" to remove a current filter. Note that the filter details
633are retained even when the filter is cleared.
634<p></p>
635For example, to sort the "All Metadata" table, choose a column, select the
636default filter setting (a Simple filter on "*"), and choose ascending or
637descending ordering.
638 <a name="importingpreviouslyassignedmetadata">
639<h3>Section 6.8: Importing Previously Assigned Metadata</h3>
640</a>
641
642This section describes how to import previously assigned metadata,
643and install parsers to handle various metadata types.
644 <p></p>
645
646If metadata in a form recognized by the Librarian Interface has been previously
647assigned to a file -- for example, when you choose documents from an existing
648Greenstone collection -- it is imported automatically when you add the file.
649To do this, the metadata must be mapped to the metadata sets available in the
650collection.
651<p></p>
652The Librarian Interface prompts for the necessary information. The prompt
653gives brief instructions and then shows the name of the metadata element that
654is being imported, just as it appears in the source file. This field cannot be
655edited or changed. Next you choose what metadata set the new element should map
656to, and then the appropriate metadata element in that set. The system
657automatically selects the closest match, in terms of set and element, for the
658new metadata.
659<p></p>
660Having checked the mapping, you can choose "Add" to add the new metadata
661element to the chosen metadata set. (This is only enabled if there is no
662element of the same name within the chosen set.) "Merge" maps the new element
663to the one chosen by the user. Finally, "Ignore" does not import any metadata
664with this element name.
665<p></p>
666Once you have specified how to import a certain piece of metadata, the mapping
667information is retained for the collection's lifetime. To correct any mistakes
668during importing, use the metadata set editor described in <a href="#editingmetadatasets">Editing Metadata Sets</a>.
669<p></p>
670For details on the metadata.xml files which Greenstone uses to store the metadata, see Chapter 2 of the Greenstone
671Developer's Guide -- Getting the most out of your documents.
672 <a name="designingacollection">
673<h1>Section 7: Designing Your Collection's Appearance</h1>
674</a>
675
676Once your files are marked up with metadata, you next decide how it should
677appear to users as a Greenstone collection. What kind of information is
678searchable? What ways are provided to browse through the documents? What
679languages are supported? Where do the buttons appear on the page? These
680things can be customized; this section describes how to do it.
681
682
683
684
685
686
687
688
689
690
691
692 <a name="thedesignview">
693<h3>Section 7.1: The Design View</h3>
694</a>
695
696This section introduces you to the design view and explains how to navigate
697between the various views within this pane.
698 <p></p>
699
700With the Librarian Interface, you can configure how the collection appears to
701the user. The configuration options are divided into different sections, each
702associated with a particular stage of navigating or presenting information.
703<p></p>
704On the left is a list of different views, and on the right are the controls
705associated with the current one. To change to a different view, click its name
706in the list.
707<p></p>
708To understand the stages and terms involved in designing a collection, first
709read Chapters 1 and 2 of the Greenstone Developer's Guide.
710 <a name="generalsettings">
711<h3>Section 7.2: General Settings</h3>
712</a>
713
714This section explains how to review and alter the general settings associated
715with your collection. First, under "Design Sections", click "General".
716 <p></p>
717
718Here the values provided during collection creation can be modified.
719<p></p>
720At the top of the page is an instruction box, which appears for each of the
721different sections. It contains a brief list of instructions to remind you
722what functionality is available.
723<p></p>
724First are the contact emails of the collection's creator and maintainer. Then
725come two checkboxes for whether the collection should be publicly accessible,
726and whether it is still under construction. The following field allows you to
727change the collection title. The next one specifies (in the form of a URL) the
728icon to show at the top left of the collection's "About" page, and the next is
729the icon used in the Greenstone library page to link to the collection. Finally
730comes the "Collection Description" text area as described in <a href="#creatingacollection">Creating A New Collection</a>.
731 <a name="plugins">
732<h3>Section 7.3: Document Plugins</h3>
733</a>
734
735This section describes how to configure the document plugins the
736collection uses. It explains how you specify what
737plugins to use, what parameters to pass to them, and in what order
738they occur. Under "Design Sections", click "Document Plugins".
739 <p></p>
740
741To add a plugin, select it using the "Select plugin to add" pull-down list near the
742bottom and then click "Add Plugin". A window appears entitled
743"Configuring Arguments"; it is described later. Once you have configured the
744new plugin, it is added to the end of the "Currently Assigned Plugins" list.
745Note that a plugin may only occur once in the list.
746<p></p>
747To remove a plugin, select it in the list and click "Remove Plugin".
748<p></p>
749Plugins are configured by providing arguments. To alter them, select the
750plugin from the list and click "Configure Plugin" (or double-click
751the plugin). A "Configuring Arguments" dialog appears with three parts: a
752text field for entering custom arguments, an area containing controls for
753specifying arguments, and two buttons at the bottom.
754<p></p>
755There are different kinds of controls. Some are checkboxes, and clicking one
756adds the appropriate option to the plugin. Others are text strings, with a
757checkbox and a text field. Click the box to enable the argument, then type
758appropriate text (regular expression, file path etc) in the box. Others are
759pull-down menus from which you can select from a given set of values. Still
760others allow multiple selections from a list. To add a value, select it and
761click "Add"; to remove it, select it and click "Remove". To learn what an
762argument does, let the mouse hover over its name for a moment and a description
763will appear.
764<p></p>
765When you have changed the configuration, click "OK" to commit the changes and
766close the dialog, or "Cancel" to close the dialog without changing any plugin
767arguments.
768<p></p>
769The plugins in the list are executed in order, and the ordering is sometimes
770important. Two plugins, ArcPlug and RecPlug, are vital to the collection
771building process, and are fixed in place at the end of the list (with a
772separator line). To change the ordering of the other ones, select the plugin you want to move
773and click "Move To Top", "Move Up", "Move Down", or "Move To Bottom".
774
775The Librarian Interface does its best to determine what arguments a plugin
776supports. However, there may be cases where the user wants to specify special
777arguments, and for this a text field called "Custom Arguments" (at the top) is
778provided. Any text in it is appended verbatim to the end of the plugin
779command.
780 <a name="searchtypes">
781<h3>Section 7.4: Search Types</h3>
782</a>
783
784This section explains how to modify a new design feature in Greenstone, Search Types, which allow fielded searching. Under "Design Sections", click "Search Types".
785 <p></p>
786
787When you enter the Search Types view, first check "Enable Advanced
788Searches", which activates the other controls. This migrates the collection to
789Greenstone 2.4 format, which supports fielded searching, and means that (a)
790the index design is different (explained in the <a href="#searchindexes">Search Indexes</a> section),
791(b) there are more text fragments to translate (see <a href="#translatetext">Translation</a>), and (c) the collection will not be usable under older Greenstone
792installations. If you later uncheck this field, most of your collection will
793be migrated back to Greenstone 2.39. However the Librarian Interface cannot
794convert the new index specifications into older ones, so you will have to
795re-enter them manually.
796<p></p>
797To add a search type, select it from the "Search Types" list and click "Add Search Type". Each type can only appear in the list once.
798<p></p>
799To remove a search type, select it from the "Currently Assigned Search Types"
800list and click "Remove Search Type". The list must contain at least
801one search type.
802<p></p>
803To change to order of a search type, select it from the list and click "Move
804Up" or "Move Down". The first one will be the default.
805 <a name="searchindexes">
806<h3>Section 7.5: Search Indexes</h3>
807</a>
808
809Indexes specify what parts of the collection are searchable. This section explains how to add and remove indexes, and set a default index. Under "Design Sections", click "Search Indexes".
810 <p></p>
811
812To add an index, type a name for it into the "Index Name" field. Select which
813of the possible information sources to index by clicking the checkboxes beside
814them. The list shows all the assigned metadata elements, as well the full
815text. Having selected the data sources, choose the granularity of the index,
816using the "At the level" menu. Once these details are complete, "Add Index"
817becomes active (unless there is an existing index with the same settings).
818Click it to add the new index.
819<p></p>
820To remove an index, select it from the list of assigned indexes and click
821"Remove Index".
822<p></p>
823The default index, the one used on the collection's search page, is tagged with
824"[Default Index]" in the "Assigned Indexes" list. To set it, select an index
825from the list and click "Set Default". To reset it, click "Clear Default".
826<p></p>
827If advanced searching is enabled (via the Search Types view), the index controls are different. Each index
828is based on just one data source. There is a new pseudo-data source "allfields" which provides searching across all specified indexes at once. Levels are not
829assigned to a specific index, but apply across all indexes: thus indexes and
830levels are added separately. Indexes are removed in the same way as above, but
831the default index can no longer be set -- it is simply the
832first index assigned.
833<p></p>
834To create indexes on all sources, click the "Add All" button. The name of each index will default to the source name. To change the name, select an index, change its details, and click "Replace Index".
835 <a name="partitionindexes">
836<h3>Section 7.6: Partition Indexes</h3>
837</a>
838
839Indexes are built on particular text or metadata sources. The search space can
840be further controlled by partitioning the index, either by language or by a
841predetermined filter. This section describes how to do this. Under "Design
842Sections", click "Partition Indexes".
843<p></p>
844The "Partition Indexes" view has three tabs; "Define Filters", "Assign
845Partitions" and "Assign Languages". To learn more about partitions read about
846subcollections and subindexes in Chapter 2 of the Greenstone Developer's Guide.
847
848
849
850
851 <a name="definefilters">
852<h3>Section 7.6.1: Define Filters</h3>
853</a>
854
855
856
857<p></p>
858
859Filters allows you to group together into a subcollection all documents in an
860index for which a metadata value matches a given pattern.
861<p></p>
862To create a filter, click the "Define Filters" tab and enter a name for the
863new filter into the "Name the subcollection filter" field. Next choose a
864document attribute to match against, either a metadata element or the name of
865the file in question. Enter a regular expression to use during the matching.
866You can toggle between "Including" documents that match the filter, or
867"Excluding" them. Finally, you can specify any of the standard PERL regular
868expression flags to use when matching (e.g. "i" for case-insensitive matching).
869Finally, click "Add Filter" to add the filter to the "Defined Subcollection Filters"
870list.
871<p></p>
872To remove a filter, select it from the list and click "Remove Filter".
873<p></p>
874To alter a filter, select it from the list, change any of the values that
875appear in the editing controls and click "Replace Filter" to commit the changes.
876 <a name="assignpartitions">
877<h3>Section 7.6.2: Assign Partitions</h3>
878</a>
879
880
881
882<p></p>
883
884Having defined a subcollection filter, use the "Assign Partitions" tab to build
885indexes for it (or for a group of filters). Select the desired filter (or
886filters) from the "Defined Subcollection Filters" list, enter a name for your partition in the "Partition Name" field, and click "Add Partition".
887<p></p>
888To remove a partition, select it from the list and click "Remove Partition".
889<p></p>
890To make a partition the default one, select it from the list and click "Set
891Default".
892<p></p>
893To clear the default partition, click "Clear Default".
894 <a name="assignlanguages">
895<h3>Section 7.6.3: Assign Languages</h3>
896</a>
897
898This section details how to restrict search indexes to particular languages.
899You do this by generating a partition using the "Assign Languages" tab of the
900"Partition Indexes" view.
901 <p></p>
902
903To add a new language to partition by, use the "Assign Languages" tab to build
904an index for it. Select the desired language from the "Language to add"
905pull-down list and click "Add Language".
906<p></p>
907To remove a language, select it from the "Language Selection" list and click
908"Remove Language".
909<p></p>
910To set the default language, select it from the list and click "Set Default".
911<p></p>
912To clear the default language, click "Clear Default".
913 <a name="xcollectionsearching">
914<h3>Section 7.7: Cross-Collection Searching</h3>
915</a>
916
917Greenstone can search across several different collections as though they were
918one. This is done by creating a "super-collection" that comprises the
919individual collections. Under "Design Sections", click "Cross-Collection Search".
920 <p></p>
921
922The Cross-Collection Search view shows a checklist of available collections. The
923current collection is ticked and cannot be deselected. To add another
924collection to be searched in parallel, click it in the list (click again to
925remove it). If only one collection is selected, there is no cross-collection
926searching.
927<p></p>
928For further details, see Chapter 1 of the Greenstone Developer's Guide.
929 <a name="classifiers">
930<h3>Section 7.8: Classifiers</h3>
931</a>
932
933This section explains how to assign "classifiers", which are used for browsing,
934to the collection. Under "Design Sections", click "Browsing Classifiers".
935 <p></p>
936
937To add a classifier, select it using the "Select classifier to add" pull-down list near the
938bottom and then click "Add Specified Classifier". A window appears entitled
939"Configuring Arguments"; instructions for this dialog are just the same as for
940plugins (see <a href="#plugins">Document Plugins</a>). Once you have configured the new
941classifier, it is added to the end of the "Currently Assigned Classifiers"
942list.
943<p></p>
944To remove a classifier, select it from the list and click "Remove Selected
945Classifier".
946<p></p>
947To change the arguments a classifier, select it from the list and click
948"Configure Selected Classifier" (or double-click on the classifier in the
949list).
950<p></p>
951The ordering of classifiers in the collection's navigation bar is reflected in
952their order here. To change it, select the classifier you want to move and
953click "Move To Top", "Move Up", "Move Down", or "Move To Bottom".
954<p></p>
955For further information on classifiers read Chapter 2, Greenstone
956Developer's Guide -- Getting the most out of your documents.
957
958The CustomAZList classifier is a special classifier that builds an alphabetical
959selection list ("AZList") and allows you to specify the letter ranges. This
960classifier has its own configuration dialogue. When a metadata element is
961selected, the "Ranges" tree automatically becomes populated with appropriate
962values. Expand or collapse the tree as desired. Select any two values and
963click "Merge" to specify a range, or select a previously merged value and click
964"Split" to restore the values contained within. When satisfied with the ranges,
965click "OK" to begin processing the documents in the collection. You can
966"Cancel" the dialog without making any changes to the collection.
967 <a name="formatstatements">
968<h3>Section 7.9: Format Features</h3>
969</a>
970
971Format commands control the structure and appearance of the collection. They
972affect such things as where buttons appear when a document is shown, and what
973links are displayed by the DateList classifier. Format commands are not easy
974to develop, and you should read Chapter 2 of the Greenstone Developer's Guide.
975This section discusses the format settings, and how the Librarian Interface
976gives access to them. Under "Design Sections", click "Format Features".
977 <p></p>
978
979You can apply a format command to anything in the "Choose Feature" pull-down
980list, which includes each classifier and a predefined list of features. When
981you select a feature, there are two types of control. Some features are simply
982enabled or disabled, and this is controlled by a checkbox. Others require a
983format string to be specified. For these there is a pull-down list ("Affected
984Component") for selecting which part of the feature the string applies to
985(if necessary), a text area ("HTML Format String") for entering the string,
986and a selection of predefined "Variables". To insert a variable into the
987current position in the format string, select it from the pull-down list and
988click "Insert".
989<p></p>
990You can specify a default format for a particular component by selecting the
991blank feature. This format is then applied to all applicable features unless
992otherwise specified.
993<p></p>
994To add a new format command, fill out the information as explained above and
995click "Add Format". The new format command appears in the list of "Currently
996Assigned Format Commands". Only one format command can be assigned to each
997feature/component combination.
998<p></p>
999To remove a format command, select it from the list and click "Remove Format".
1000<p></p>
1001To change a format command, select it from the list, modify the settings, and
1002click "Replace Format".
1003<p></p>
1004For more information about variables and the feature components, read Chapter 2
1005of the Greenstone Developer's Guide.
1006
1007If the "Allow Extended Options" checkbox is ticked, some advanced formatting options are enabled. The list of features that can be formatted is changed slightly, and more variables are available to be used in the format command, providing greater control over the page layout.
1008 <a name="translatetext">
1009<h3>Section 7.10: Translate Text</h3>
1010</a>
1011
1012This section describes the translation view, where you can define
1013language-specific text fragments for parts of the collection's interface.
1014Under "Design Sections", click "Translate Text".
1015 <p></p>
1016
1017First choose the an entry from the "Features" list. The language-specific
1018strings associated with this feature appear below. Use the "Language of
1019translation" pull-down list to select the target language, and type the
1020translated text into the text area, referring to the "Initial Text Fragment" if
1021necessary. Click "Add Translation" when finished.
1022<p></p>
1023To remove an existing translation, select it in the "Assigned Translations"
1024table and click "Remove Translation".
1025<p></p>
1026To edit a translation, select it, edit it in the "Translated Text" text
1027area, and click "Replace Translation".
1028 <a name="metadatasets">
1029<h3>Section 7.11: Metadata Sets</h3>
1030</a>
1031
1032This section explains the metadata set review panel.
1033Under "Design Sections", click "Metadata Sets".
1034 <p></p>
1035
1036This view is used to review the metadata sets that the collection uses, and the
1037elements that are available within each set. Choose from the list of "Available
1038Metadata Sets" in order to see details of their elements. This view is
1039read-only.
1040 <a name="producingthecollection">
1041<h1>Section 8: Producing Your Collection</h1>
1042</a>
1043
1044Having collected the documents for the collection, annotated them with
1045metadata, and designed how the collection will appear, you can now produce the
1046collection using Greenstone. This section explains how.
1047
1048
1049
1050
1051 <a name="thecreateview">
1052<h3>Section 8.1: The Create View</h3>
1053</a>
1054
1055
1056
1057<p></p>
1058The Create view is used to create the collection by running Greenstone
1059collection-building scripts on the information you have provided. This is
1060generally straightforward: just click "Build Collection" at the bottom of the
1061screen. However, the building process can be customized. You can also use
1062this view to review details of previous attempts to build this collection,
1063whether successful or not.
1064<p></p>
1065The buttons for building and cancelling the building process are at the bottom.
1066Above appears a group of controls titled "Collection Import &amp; Build Options".
1067To the left is a list of three items, and to the right is a pane that reflects
1068the currently chosen item in the list, as described in the following sections.
1069<p></p>
1070Clicking "Build Collection" initiates the collection building process. The time
1071this takes depends on the size of the collection and the number of indexes
1072being created (for huge collections it can be hours). To cancel the process at
1073any time, click "Cancel Build".
1074 <a name="buildsettings">
1075<h3>Section 8.2: Import and Build Settings</h3>
1076</a>
1077
1078This section explains how to access the various import and build settings.
1079For more information of importing and building read Chapter 1 of the Greenstone
1080Developer's Guide -- Understanding the collection-building process.
1081 <p></p>
1082
1083The first two entries in the list on the left are "Import" and "Build", which
1084give settings that apply to the import and build scripts respectively.
1085<p></p>
1086Controlling the various settings is done in a similar way to the
1087"Configuring Arguments" window described in the <a href="#plugins">Document Plugins</a> section. Some
1088fields require numeric arguments, and you can either type these in or use the
1089up and down arrows to increase or decrease the current value (in some cases,
1090the interface restricts the range you can enter). Others are enabled by
1091clicking a checkbox (click again to disable).
1092 <a name="messagelog">
1093<h3>Section 8.3: Message Log</h3>
1094</a>
1095
1096
1097
1098<p></p>
1099
1100The third item on the left is "Message Log". This shows the output that
1101Greenstone generated when it built the collection before. Select the
1102log you want by clicking on the desired date in the "Log History" list.
1103 <a name="theprogressview">
1104<h3>Section 8.4: The Progress View</h3>
1105</a>
1106
1107
1108
1109<p></p>
1110
1111When you start to build a collection, the view changes immediately. The
1112controls described <a href="#thecreateview">previously</a> are replaced by two
1113progress bars and a text area. The bars indicate progress through the import
1114phase, then the build phase. The text area shows the Message Log mentioned in
1115the <a href="#messagelog">previous section</a>.
1116 <a name="previewingthecollection">
1117<h1>Section 9: Previewing the Collection</h1>
1118</a>
1119
1120
1121
1122 <a name="thepreviewview">
1123<h3>Section 9.1: The Preview View</h3>
1124</a>
1125
1126
1127
1128<p></p>
1129
1130Once you have built a collection the "Preview" tab on the main screen becomes
1131enabled. This allows you to inspect the new collection. It shows a simplified
1132Web browser with initial page (and home page) set to the new collection's "About" page. You can navigate the collection using standard hyperlink clicks.
1133 <a name="miscellaneous">
1134<h1>Section 10: Miscellaneous</h1>
1135</a>
1136
1137This section describes features of the Librarian Interface that are not associated
1138with any particular view.
1139
1140
1141 <a name="preferences">
1142<h3>Section 10.1: Preferences</h3>
1143</a>
1144
1145This section explains the preferences dialog, accessed by opening "File" -&gt; "Preferences".
1146 <p></p>
1147
1148There are three "General" options. If "View Extracted Metadata" is checked, the
1149various controls dealing with metadata always show all metadata that has been
1150extracted automatically from documents. Deselecting it hides this metadata
1151(although it is still available during collection design, and within the
1152final Greenstone collection).
1153<p></p>
1154If "Show File Size" is checked, the file size is shown next to each file in the Workspace and Collection file trees in the Gather and Enrich views.
1155<p></p>
1156The third "General" option is a pull-down list of the various languages that
1157the Librarian Interface can be presented in. These correspond to the
1158dictionaries located in the "classes" folder of the Librarian Interface's
1159directory. If you change the dictionary by choosing one from the list, you must
1160restart the Librarian Interface in order to load the new language strings from
1161the dictionary.
1162<p></p>
1163The Librarian Interface can support different workflows by determining which of
1164the various view tabs are visible. Use the "Workflow" tab to customise what
1165views are available by checking the boxes next to the views that you want to be
1166available. Alternatively, use the pull-down list at the bottom to select
1167predetermined configurations. Closing the preferences dialog establishes these
1168workflow settings. These settings are stored with the collection, not in the
1169Librarian Interface configuration file.
1170<p></p>
1171The "Connection" tab lets you alter the path to the locally-running Greenstone
1172library server, which is used when Previewing collections. It also lets you set
1173proxy information for connecting to the Internet (e.g. when Browsing or
1174Mirroring your files; see 3.0 and 4.0 for details). Check the box to enable
1175proxy connection and supply details of the proxy host address and port number.
1176The proxy connection is established when you close the Preferences dialog.
1177<p></p>
1178During the course of a session the Librarian Interface may give warning
1179messages which inform you of possibly unforeseen consequences of an action. You
1180can disable the messages by checking the "Do not show this warning again" box.
1181You can re-enable warning messages using the "Warnings" tab. Check the box
1182next to warning messages you want to see again.
1183 <a name="fileassociations">
1184<h3>Section 10.2: File Associations</h3>
1185</a>
1186
1187The Librarian Interface uses particular application programs to open particular
1188file types. This section explains how to assign and edit these file
1189associations.
1190 <p></p>
1191
1192To alter file associations open the "File" menu and click "File
1193Associations...".
1194<p></p>
1195To add an association, select the target file extension from the pull-down
1196list, or type in a new extension (do not include the "."). Next either type
1197command that launches the desired application in the appropriate field, or
1198choose the application from the "Browse" dialog. "%1" can be used in the launch
1199command to insert the name of the file being opened. Once these are filled out,
1200"Add Association" is enabled and can be clicked to add the association.
1201<p></p>
1202To edit an association, select an existing file extension. Any existing
1203associated command is shown in the launch command field. Edit it, and then
1204click "Replace Association".
1205<p></p>
1206To remove an association, select an existing file extension and click "Remove Association".
1207(The file extension remains in the "For Files Ending" pull-down list.)
1208<p></p>
1209File associations are stored in the Librarian Interface's main folder, in a file
1210called "associations.xml".
1211 <a name="metadatasetandprofileediting">
1212<h1>Section 11: Metadata Set and Profile Editing</h1>
1213</a>
1214
1215This section explains how to edit metadata sets used by the Librarian
1216Interface. This is the only way to remove a value from the "Previous Values"
1217tree. Although you can use the Enrich view to remove a certain value
1218from a record, the value remains in the value tree. To remove it (or any
1219part of the metadata set, including its elements), use the metadata set editor.
1220<p></p>
1221The same tool is used to alter the instructions that map metadata from files
1222imported into the collection to existing metadata sets. These are called
1223"importing profiles".
1224<p></p>
1225To edit a metadata set or importing profile, choose "Metadata Sets" from the menu
1226bar and select the "Edit Set" action.
1227
1228
1229 <a name="editingmetadatasets">
1230<h3>Section 11.1: Editing Metadata Sets</h3>
1231</a>
1232
1233
1234
1235<p></p>
1236
1237On the left of the "Edit Metadata Sets" dialog is a list showing what metadata
1238sets and profiles can be edited. Click one of these and its details will
1239appear on the right in one or more tables. Beneath are buttons for adding,
1240editing or removing the various parts; alongside them is the "Close" button.
1241Many buttons are greyed out initially, and are activated by selections in the
1242tables. Now we describe how to edit sets and elements.
1243<p></p>
1244To define a new metadata set, beside "Set" click "Add", fill out the
1245information requested, and click "OK". "Namespace" is a short identifier for
1246the new set (e.g. "dc" for Dublin Core; "dls" for the Development Library
1247Subset).
1248<p></p>
1249To remove a metadata set, select it in the list on the left and click "Remove".
1250A confirmation prompt will appear; confirming it permanently
1251removes the set and all associated metadata.
1252<p></p>
1253Some information is associated with each metadata set, such as its creator and
1254creation date. We call these "attributes" of the metadata set, and you can
1255alter them.
1256Beside "Attribute", click "Add" to add an attribute to the selected metadata
1257set, fill in the requested information -- name, language and values -- and
1258click "OK". Each metadata set is considered unique, so for a new metadata set
1259the pull-down list for the name and value are initially empty. Beside
1260"Attribute", "Edit" becomes active when an attribute is selected in the table
1261and leads to the same dialog as "Add" (except that the current value is already
1262filled out). Beside "Attribute", "Remove" becomes active when the attribute is
1263selected; when clicked the attribute is removed.
1264<p></p>
1265Double clicking on a set in the list on the left will display a list of metadata elements in that set. You can add an element, remove it, and remove values from
1266it. To add an element, beside "Element" click "Add" and specify the new
1267element's name.
1268<p></p>
1269To remove a metadata element, select it and beside "Element" click "Remove".
1270This permanently removes the element and all metadata
1271associated with it.
1272<p></p>
1273Just as information is associated with each metadata set, information can also
1274be associated with each metadata element -- metadata about metadata! Again we
1275call these "attributes"; Examples are a language-specific name for the element,
1276its definition, or perhaps a general comment.
1277<p></p>
1278You edit the attributes of an element in the same way that you edit the
1279attributes of a metadata set, explained above. In this case the pull-down
1280lists in the add and edit prompts may contain values from the same attribute of
1281other elements within the set.
1282<p></p>
1283You can also alter the "value tree" for an element, which
1284contains all the values that have been assigned to it. You
1285can "Add" a value whenever an element is selected. Choose a parent folder
1286(if any), enter the value and click "OK" to put the
1287new value in the tree. You can "Edit" a value that you have selected in the
1288value tree; click "OK" to commit the changes. Note that changing the parent
1289subject will cause the value to be moved to that subject. You can "Remove" a
1290value that you have selected in the tree -- but note that this does
1291not remove all metadata referring to this value, and if the
1292value is still in use it will be restored the next time you save.
1293<p></p>
1294Once you have finished changing the metadata set, click "Close".
1295 <a name="editingimportprofiles">
1296<h3>Section 11.2: Editing Metadata Import Profiles</h3>
1297</a>
1298
1299
1300
1301<p></p>
1302
1303Double-click the "Importing Profiles" item to see a list of importing profiles
1304for importing from other collections into this one. Each profile is named
1305after the collection to which it applies -- that is, the collection that
1306documents are coming from. You can add a profile by clicking "Add" beside
1307"Profile" and specifying the name of the collection that it should apply to. You
1308can remove a profile by selecting it and click "Remove" beside "Profile".
1309<p></p>
1310When a profile is selected, its mapping table appears. Each line gives a
1311correspondence between a metadata element in the collection that the metadata
1312comes from, and a metadata element in the collection being constructed. You
1313can edit this table. To add a new mapping, select a source profile, then click
1314"Add" beside "Attribute". The standard attribute dialog box appears, except
1315that the language field is disabled and the "Values" pull-down list contains
1316all the elements currently available in the collection. Mappings can be edited
1317and removed as described above.
1318<p></p>
1319Once you have finished changing the metadata importing profile, click "Close".
1320 </body>
1321</html>
1322
Note: See TracBrowser for help on using the repository browser.