- Timestamp:
- 2007-05-25T16:12:13+12:00 (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gsdl-documentation/manuals/xml-source/en/User_en.xml
r13869 r14099 62 62 </Bullet> 63 63 </BulletList> 64 </Content> 65 </Section> 66 <Section id="copyright"> 67 <Title> 68 <Text id="copyright-title">Copyright</Text> 69 </Title> 70 <Content> 71 <Text id="right-text-1">Copyright 2002 2003 2004 2005 2006 2007 by the <Link url="http://www.nzdl.org">New Zealand Digital Library Project</Link> at <Link url="http://www.waikato.ac.nz">the University of Waikato</Link>, New Zealand.</Text> 72 <Text id="right-text-2">Permission is granted to copy, distribute and/or modify this document under the terms of the <Link url="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License</Link>, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled <Link url="http://greenstonewiki.cs.waikato.ac.nz/wiki/gsdoc/GNUFDL.html">âGNU Free Documentation License.â</Link></Text> 64 73 </Content> 65 74 </Section> … … 681 690 <Text id="193">Care is taken to deal appropriately with name clashes when files of the same name in different parts of the computer's directory structure are copied into the same folder of the collection.</Text> 682 691 <Text id="194">In Figure <CrossRef target="Figure" ref="exploring_the_local_file_space"/> the user is using the interactive file tree display to explore the local file system. At this stage, the collection on the right is empty; the user populates it by dragging and dropping files of interest from the left to the right panel. Such files are âcopiedâ rather than âmovedâ: so as not to disturb the original file system. The usual techniques for multiple selection, dragging and dropping, structuring the new collection by creating subdirectories (âfoldersâ), and deleting files from it by moving them to a trashcan, are all available.</Text> 683 <Text id="195">Existing collections are represented by a subdirectory on the left called âGreenstone Collections,â which can be opened and explored like any other directory. However, the documents therein differ from ordinary files because they already have metadata attached, and this is preserved when they are moved into the new collection. Conflicts may arise because their metadata may have been assigned using a different metadata set from the one in use for the new collection, and the user must resolve these. In Figure <CrossRef target="Figure" ref="importing_existing_metadata"/> the user has selected some documents from an existing collection and dragged them into the new one. The popup window explains that the metadata element <i>Organization</i> cannot be automatically imported, and asks the user to either select a metadata set and press <i>Add</i> to add the metadata element to that set ,<FootnoteRef id="1"/>or choose a metadata set, then an element, and press <i>Merge</i> to effectively rename the old metadata element to the new one by merging the two. Metadata in subsequent documents from the same collection will automatically be handled in the same way.</Text>692 <Text id="195">Existing collections are represented by a subdirectory on the left called âGreenstone Collections,â which can be opened and explored like any other directory. However, the documents therein differ from ordinary files because they already have metadata attached, and this is preserved when they are moved into the new collection. Conflicts may arise because their metadata may have been assigned using a different metadata set from the one in use for the new collection, and the user must resolve these. In Figure <CrossRef target="Figure" ref="importing_existing_metadata"/> the user has selected some documents from an existing collection and dragged them into the new one. The popup window explains that the metadata element <i>Organization</i> cannot be automatically imported, and asks the user to either select a metadata set and press <i>Add</i> to add the metadata element to that set<FootnoteRef id="1"/>, or choose a metadata set, then an element, and press <i>Merge</i> to effectively rename the old metadata element to the new one by merging the two. Metadata in subsequent documents from the same collection will automatically be handled in the same way.</Text> 684 693 <Text id="196">When large file sets are selected, dragged, and dropped into the new collection, the copying operation may take some timeâparticularly if metadata conversion is involved. To indicate progress, the interface shows which file is being copied and what percentage of files has been processed.</Text> 685 694 <Text id="197">Special facilities are provided for dealing with large file sets. For example, the user can choose to filter the file tree to show only certain files, using a dropdown menu of file types displayed underneath the trees. In Figure <CrossRef target="Figure" ref="filtering_the_file_trees"/>, only the HTM and HTML files are being shown (and only these files will be copied by drag and drop).</Text>
Note:
See TracChangeset
for help on using the changeset viewer.