Archivematica - User contributions [en]

Improvements/aipreadme

2017-06-20T19:18:52Z

Dan: minor fixes to formatting

== User story ==

As a repository manager, I would like AIP's to be as self describing as possible, so that future users, with little or no information about Archivematica or what an AIP is, will be able to understand the structure and contents of the AIP's I produce now.

== Status ==

2017-06-01 - New Proposal

== Interest ==

If you'd like to get involved in this development, please feel free to contribute to this wiki page or start a discussion on our [https://groups.google.com/forum/#!forum/archivematica| user forum].

== Analysis: ==

Currently, Archivematica AIP's are structured as a Bag (https://tools.ietf.org/html/draft-kunze-bagit-14) and contain a METS file, which describes the contents of the AIP. Details about the Archivematica AIP structure are here: https://www.archivematica.org/en/docs/archivematica-1.6/user-manual/archival-storage/aip-structure/

METS files are machine readable, but are not human friendly formats.

Adding a human readable index or description into an AIP would improve the chances of a future user understanding the structure.

Archivematica structures AIP's in a specific way, but that is not documented within the AIP. Adding more explicit documentation about the structure would help users test that AIP's are valid, and help them to understand the structure.

There is a similar proposal outlined here: https://github.com/UTS-eResearch/datacrate

=== Use case: Add a README to each AIP ===

In the data/ directory (beside the mets file) add a README.html or README.md file. This would be intended as the first file to be opened by a human being trying to examine an AIP.

The README file would include
* some boilerplate text, describing what an AIP is
* links to the Archivematica documentation, to METS documentation, to PREMIS docs, etc.
* a link to the METS file
* optionally a link to a CATALOG.html file, that includes more detailed information about the contents of the AIP.

====Sample README file text====

This readme file describes the basic structure of an Archival Information Package (AIP) generated by Archivematica.

'''Acronyms'''

<p>AIP = Archival Information Package</p>
<p>METS = Metadata Encoding and Transmission Standard</p>
<p>OAIS = Open Archival Information System</p>
<p>PDI = Preservation Description Information</p>
<p>PREMIS = Preservation Metadata Implementation Strategies</p>
<p>UUID = Unique Universal Identifier</p>

'''Introduction'''

Archivematica is an open-source suite of tools designed to ingest diverse digital content and prepare AIPs for long-term storage. Once an AIP is generated it is not dependent on Archivematica for retrieval, and can be opened using any standard file browser. The concept of an AIP is derived from the ISO 14721:2012 ''Reference Model for an Open Archival Information System (OAIS)'', which defines it as “[a]n Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.”

'''Content Information'''

In an Archivematica AIP, the Content Information consists primarily of the originally ingested digital objects and any preservation versions of the objects created to mitigate the risk of format obsolescence over time. The preservation copies typically have the same filenames as the original objects but with different file extensions and with UUIDs appended to the filename. For example, for an original file named ''BBhelmet.ai'' the preservation version may be named ''BBhelmet-e3a3988d-8149-49ea-adc5-c255fb68d4f9.pdf''.

The originally ingested digital objects and any preservation versions are located in the ''objects'' directory of the AIP. There will be nested subdirectories in the ''objects'' directory if these subdirectories were included in the original transfer or added during SIP arrangement. The ''objects'' directory also includes a ''submissionDocumentation'' folder and a ''metadata'' folder. The ''submissionDocumentation'' folder contains documentation such as donor agreements and transfer forms, if these are included in the AIP, as well as a METS file that records the contents of the original transfer(s) from which the AIP was created. The ''metadata'' folder holds any metadata files included in the original transfer(s), and any OCR text files generated during processing.

'''Preservation Description Information (PDI)'''

The PDI in an Archivematica AIP is recorded in a METS XML file. METS is maintained by the Library of Congress, which defines it as “a standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium.” In the Archivematica AIP the METS filename is composed of the name METS with a UUID file extension and an XML file extension; for example ''METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml''. The METS file typically consists of the following standard METS sections:
<p><mets:metsHdr> (METS header): basic information about the METS file;</p>
<p><mets:dmdSec> (descriptive metadata section): descriptive metadata about the digital objects;</p>
<p><mets:amdSec> (administrative metadata section): technical and provenance information about the digital objects;</p>
<p><mets:fileSec> (file section): a list of the digital objects and an indication of their role in the AIP (original, preservation, metadata, submission documentation, license etc.);</p>
<p><mets:structMap> (structural map): a physical or logical ordering of the digital objects.</p>

The technical and provenance information in the METS amdSec is recorded as PREMIS metadata. PREMIS is also a Library of Congress standard, and is described as "the international standard for metadata to support the preservation of digital objects and ensure their long-term usability." The PREMIS entities are wrapped in the METS file as follows:

<p><mets:amdSec></p>
<p>--<mets:techMD> (technical metadata)</p>
<p>----<premis:object> e.g. UUID, size, checksum, format, original name, extracted technical metadata</p>
<p>--<mets:digiprovMD> (digital provenance metadata)</p>
<p>----<premis:event> e.g. ingestion, message digest calculation, virus scan, format identification, validation, normalization, fixity check</p>
<p>----<premis:agent> for each PREMIS Event there are three associated Agents: the organization, the digital preservation system (e.g. Archivematica 1.x) and the logged-in user</p>
<p>--<mets:rightsMD> (rights metadata)</p>
<p>----<premis:rights> Rights pertaining to the preservation, reproduction and use of the preserved digital objects (only included if the user added rights metadata prior to or during ingest)</p>

The fileSec and structMap use identifier attributes to link a digital object to its amdSec and (if used) dmdSec. For example, if a file entry in the fileSec has the attribute ''ADMID="amdSec_1"'' this means that the amdSec with the identifier ''amdSec_1'' contains the administrative (i.e. technical and provenance) metadata for that file. The fileSec also uses a group identifier attribute to indicate relationships between digital objects. For example, if file A in ''fileGrp "USE=original"'' and file B in ''fileGrp "USE="preservation"'' both have the group identifier attribute ''"Group-269b494d-01cb-451b-8d5e-590d57126d3d"'', then file B is a preservation version generated from file A.

'''AIP structure'''

An Archivematica AIP is packaged into a bag in accordance with the IETF Trust ''BagIt File Packaging Format'', and contains some contents not described in the sections above. This tree structure depicts a typical Archivematica AIP:

<pre>
(1) AIP-name-e3a3988d-8149-49ea-adc5-c255fb68d4f9
(2) ├── bag-info.txt
(3) ├── bagit.txt
(4) ├── manifest-sha512.txt
(5) ├── tagmanifest-md5.txt
(6) └── data
(7) ├── logs
(8) ├── objects
(9) ├── thumbnails
(10) ├── METS.0ad8cdab-dbbf-4863-8a4d-9a675c227216.xml
(11) └── README.txt
</pre>

(1) AIP root directory, with an appended UUID</p>
(2)-(5) Standard packaging files produced in accordance with the BagIt specification.</p>
(6) data directory - this is also a standard directory specified by the BagIt specification. The data directory contains the AIP Content Information and PDI</p>
(7) logs directory - contains log outputs of some of the tools that Archivematica uses in generating the AIP</p>
(8) objects directory - contains the original digital objects as well as normalized versions</p>
(9) thumbnails directory - contains thumbnails generated from the original object for use in the Archivematica user interface</p>
(10) the Archivematica METS file</p>
(11) this README text file</p>

=== Use case: Create and Use a Bag Profile ===

https://github.com/ruebot/bagit-profiles

Archivematica could define a bag profile and reference this in the AIP's it produces. This would help make AIP's more easily machine readable.

Appraisal Arrangement tab

2017-01-19T00:06:17Z

Dan: Add link to Improvements page

[[Main Page]] > [[Development]] > [[Requirements]] > Appraisal and Arrangement Tab

== Background ==

The Bentley Historical Library has a Mellon grant which is sponsoring development on the foundational project to create an Appraisal and Arrangement tab. This tab will function as a place between Transfer and Ingest where archivists can make archival appraisal decisions with material from Transfer, and structure an arrangement for the SIP before starting Ingest processes. As of the Archivematica 1.3.0 release, the arrangement/appraisal decisions are made at the top of the Ingest tab by selecting transfers from the [https://www.archivematica.org/en/docs/archivematica-1.3/user-manual/ingest/ingest/#arrange-sip backlog for arrangement]. This process, including the transfer backlog search, is to be moved into the new Appraisal and Arrangement tab.

Older requirements for similar functionality:
* [[Transfer and SIP creation]]
* [[Transfer backlog requirements]]

=== Interim development ===

Mid-way development feedback is available as a narrative [https://docs.google.com/document/d/1LZ0D1HbVRM4JDzj84ANK0XRsO0Z13LFlRKhS6yQjLi4/edit# here] and as an itemized spreadsheet [https://docs.google.com/spreadsheets/d/1UvATSsHJUJh9A-3CxHVJnCI_zArTh5aQXFpUvUjyxKc/edit#gid=75756948 here].

== Requirements ==

=== Data ===

Data gathered during the Transfer stage has the potential to be used in the Appraisal/Arrangement tab for reports and visualizations. Below is a (currently unordered) list of potentially required data:

* What data points about the objects themselves? Filename, format, MIME type, other?
* Bulk Extractor reports (which ones? how to view?)
* Directory printer text file -or- METS.xml structMap (same info)
* File format information (grouped by file extension? by PRONOM ID?)
* Size of content (space on disk), number of files
* Viewer based on format ID
* logs (virus scan, format identification, etc)
* Other?

=== ArchivesSpace resources ===
See also [[ArchivesSpace_integration|ArchivesSpace integration requirements]]

How will ArchivesSpace resources be displayed for matching? Questions for requirements gathering:

* How many resources and at what level should be loaded in the tab?
* What options does the user have to search for existing resources?
* How does the user create a new resource?
* What data points are displayed (labels, level of description, other)?

=== Querying/filtering ===

What are the requirements for querying or filtering the data gathered above?

=== Workflow questions ===

These are some questions related to workflow that have arisen since the early development of the Tab:

Given the ability to produce a refined list of digital objects in the File List pane:

1. Is it necessary to be able to filter by format or PUID from the backlog, or only from the refined list?

Sample workflow:
* User performs search of backlog and populates backlog pane
* User selects transfers relevant to their purpose
* User '''then''' filters the selected transfers by a specific file type, which populates the File List pane?

'''Answer''': Selections from the backlog pane inform what shows up on the analysis pane and selections from the analysis pane in turn inform what shows up in the file list. Actually, that's why we'd like to be able to click on more than one piece of the pie at a time, or on more than one file type from the report at a time, or on a FPR group.

2. From where does a user drag files in order to create a SIP? From backlog, the File List pane, or both?

'''Answer''': In our discussions, the user would drag and drop from the backlog. This is because, at least for us, arrangement will most likely be based on the original directory structure or the tags we've applied, but probably not often on something like file format or type (important for appraisal to be sure, but not so much, at least for us, for arrangement). As such, dragging and dropping right from the file list isn't something we really considered.

For an example of a workflow that might use the Appraisal tab and the Archivematica/ArchivesSpace integration see [[Archivematica to ArchivesSpace Workflow]]

== User Stories ==

These are some user stories added during development as final requirements are being defined:

'''Moving Files to Different Digital Object Components'''

As an archivist, I need to move files dragged to a resource in the ArchivesSpace pane to different locations in the arrangement, so that I can change the arrangement as new relationships become apparent. Without this ability, I would need to think about and note the arrangement of files before beginning to drag them from a package in the backlog and would not easily be able to fix mistakes.

'''Adding Multiple Files to a Digital Object Component'''

As an archivist, I need to drag a folder of files from a package in the backlog to the same digital object component, so that I can easily add large numbers of items to a resource without having to move each file individually. For this reason, I also need to be able to drag multiple selected files within a folder from a transfer package to a digital object component.

'''Controlling File Order Under Digital Object Components'''

As an archivist, I need to be able to control the order of items grouped under digital object components in the Appraisal tab, so that I can order the items in a way that is meaningful to understanding the files and/or conducive to users finding items. It would be helpful if Archivematica defaulted to sorting alphanumerically by filename but also allowed me to change the order manually.

== Mockups ==

'''Version 1 of the transfer backlog/reporting pane:'''

[[Image:Appraisal_Arrangement_tab_pane_mockups_-_Transfer_backlog_pane.png|700 px]]

'''Screenshots during interim development period, July 2015:'''

[[Image:a_a_tab_July2015_1.png|700 px]]

[[Image:a_a_tab_July2015_2.png|700 px]]

New functionality identified during this period includes tagging content while processing the backlog, as an "aide memoire"- in this example, a reminder that some material will be discarded from the accession.

[[Image:a_a_tab_July2015_3.png|700 px]]

Detail of potential ArchivesSpace workflow- editing metadata to change title, date, level of description and general note.

[[Image:ArchivesSpace_workflow.png|700 px]]

'''Screenshots taken during development January/February 2016'''

Files from packages sent to the backlog in Archivematica can be dragged to digital object components which have been added to archival objects in the ArchivesSpace pane.

[[Image:Feb2016 Backlog ArchivesSpace panes.png|700 px]]

Tags can be added to files in the backlog.

[[Image:Feb2016 adding tags.png|500 px]]

Files selected in the backlog appear in the Analysis pane which can be used to populate the File List pane. Tags can also be added here.

[[Image:Feb2016 Analysis FileList panes.png|700 px]]

The Analysis pane also includes options for creating visualizations.

[[Image:Feb2016 Analysis pane visulalization.png| 700 px]]

== Technical architecture ==

An initial mockup of the appraisal tab has been started, developed as an Angular.js app. The code is available on [https://github.com/artefactual-labs/appraisal-tab github].

The basic idea is to create an Angular app, that communicates with the Archivematica Dashboard via its REST api.

More details [[Appraisal Tab Architecture]]

== Improvements ==

For discussion about possible enhancements to the Appraisal arrangement tab, see:

* [[Improvements/Appraisal]]

Improvements/Appraisal

2017-01-18T23:55:53Z

Dan: fix page category

This page includes development ideas and wireframes for enhancements to the '''Appraisal and arrangement tab''', introduced in Archivematica 1.6. For more information on the development of the Appraisal tab, see:

* [[Appraisal_Arrangement_tab]]

==Usability enhancements==

The following wireframes were produced in January 2016 as part of the original development project that lead to the creation of the Appraisal and Arrangement tab, via sponsorship from the Bentley Historical Library at the University of Michigan. Unfortunately, the project ran out of hours, and these usability enhancements were never implemented. We have added the wireframes here for discussion, inspiration, and possible future enhancement.

'''Unannotated version'''

[[Image:appraisal-tab-view1-v002-2016-01-14.png|700 px]]

'''Annotated Version'''

[[Image:annotated-appraisal-tab-view1-v002-2016-01-14.png|700 px]]

----

* [[Improvements|Back to improvements]]
* [[Main Page|Archivematica wiki home]]

[[Category:Development documentation]]

2012-10-01T17:52:13Z

Dan: /* Start Archivematica virtual appliance */

[[Main Page]] > Virtual appliance instructions

= Distribution as a Virtual Appliance =

Archivematica is distributed as a [http://en.wikipedia.org/wiki/Virtual_appliance virtual appliance] which integrates a number of software tools into one common virtual machine environment. A virtual appliance is one file containing a minimal operating system and server software. You can "play" this file with a free virtual machine player like VMware Player or Sun VirtualBox.

This allows Archivematica to be run on almost any workstation or server hardware without compromising the host machine's operating system or application software. At the same time, the virtual appliance is able to interact with any number of networked and/or external storage devices to allow for the flexible implementation of an archival storage and backup strategy.

*See the [[software]] page for a full list of the tools used in each system release.
*See the [[documentation]] page for instructions on how to use the virtual appliance to accomplish the system [[requirements]].
</br>

=Minimum hardware requirements=

*Processor: Intel core 2 or AMD Opteron
*Memory: 1 GB for the virtual appliance ('guest') operating system, i.e: if the 'host' operating system has 2 GB available, 1 GB needs to allocated to the 'guest'. Depending on the operating system, machines with less than 2 GB total memory will likely have trouble running Archivematica. Note that the default allocation setting in Archivematica is 512 MB; however, the more that is allocated the better the system will run. The setting can be changed once Archivematica is running.
*Hard Drive space: a minimum of 3 GB to test the system on a small scale (i.e. use the available test files or import a small set of test files); 12 GB or more for larger implementations

</br>

=Instructions for using the VM image in VirtualBox=

==Install Oracle Virtual Box==

*Archivematica uses the [http://en.wikipedia.org/wiki/Open_Virtualization_Format Open Virtualization Format] and has been tested with the free and open-source [http://www.sun.com/software/products/virtualbox/index.jsp Oracle Virtual Box ] virtualization platform.
*There are VirtualBox versions available for every major operating system.
**Download and install Oracle VirtualBox: [http://dlc.sun.com/virtualbox/vboxdownload.html http://dlc.sun.com/virtualbox/vboxdownload.html]. Note that if you are installing VirtualBox on Windows you will have to click through a number of warnings that you are attempting to install non-verified software.

==Download Archivematica ==

*[http://archivematica.org/download Download] the latest version of the Archivematica appliance.
*Unzip the Archivematica file. This should result in the following file appearing in an Archivematica folder:
**archivematica-0.9-beta.vmdk
[[File:extracting_archivmatica-vmdk-tbz.png]]
</br>
<div class="note">
<strong>Remember:</strong>
</br>
Be sure to take note of what location on your computer you choose to extract the file, so you can browse to it later when setting up the virtual appliance (instructions below).
</div>
</br>

== Start Archivematica virtual appliance ==

<ol>
<li>Open the Oracle VirtualBox virtual machine.</li>
<li>Click New</li>
<li>Click Next</li>
[[File:new_next_VMWizard.png]]
<li>Set the name and type OS type (archivematica, linux-ubuntu)</li>
[[File:2_VM_Name_OS_type.png]]
<li>Click Continue / Next</li>
<li>Set Memory to 1 GB (1024 MB) or higher</li>
[[File:3_set_memory.png]]
<li>Click Continue</li>
<li>Select 'Use existing hard disk' and browse to and select archivematica-0.9-beta.vmdk</li>
[[File:4_use_exist_hardisk_select_archivematica.png]]
<li>Click Continue. Review Summary and Click Create</li>
[[File:5_review_click_create.png]]
<li>The virtual box will open with Archivematica 0.9-beta listed on the left-hand side (in some cases "archivematica" will be listed on the left-hand side). Select Archivematica 0.9-beta and click Start (the green arrow in the menu).</li>
[[File:6_start_archivematica_VM.png]]

<div class="note"><strong>USB Warning at Startup?</strong>
</br>
[[File:error_USB_setup.png]]
</br>

Depending on the setup and configuration of your computer peripherals, you may get this warning the first time you try to launch the Archivematica virtual appliance. Don't worry - it has nothing to do with the installation. We suggest simply checking "Don't show this message again," clicking OK, and proceeding. If you do want some guidance on troubleshooting USB detection in the Virtualbox, you can look at Oracle's troubleshooting instructions for USB detection in Linux [http://www.virtualbox.org/manual/ch12.html#ts_usb-linux here].
</div>
</br>
<li>As the virtual appliance starts, you may have to select your machine from the list of available options. Hit return.
</br>
[[File:inside_the_VM.png]]
<li>The image should launch, showing you a Linux Ubuntu desktop Login screen using the user name ''demo'' and the password ''demo''. (on slower systems hitting return may cause the windows to reset, this is being addressed)</li>
[[File:archivematica_virtualapp_login.png]]
<li>From here it is suggested that you use your external browser to access the archivematica dashboard (see '''Ubuntu login reset issue''', below)</li>

* Log into the Archivematica dashboard using the user name ''demo'' and the password ''demo''.
* If your mouse pointer does not appear to be working in the virtual machine, click the letter f while holding down the right-hand control button. Do the same thing to switch back to using your mouse pointer outside the virtual box.

<li>Congratulations, you have a running copy of Archivematica! See [[Documentation]] for instructions on how to use the software.</li>
</ol>
</br>
<div class="note">
'''Important:'''</br> Archivematica may appear to crash when used as a virtual appliance. See Ubuntu login reset issue, below.
</div>

==Ubuntu login reset issue==
*Due to an issue with the Ubuntu 12.04.1 desktop, Archivematica may appear to crash when in use. The user will see a brief display of dingbat characters in the terminal, followed by a return to the Ubuntu login. Logging in will restore the dashboard and the user can continue processing. To avoid this issue, you can add settings to allow the Archivematica dashboard and ICA-AtoM to be accessed from your web browser, outside of the virtual machine. The steps are as follows:

<ol>
<li> Shut the virtual machine down if it is open.
<li> In virtualbox select the archivematica virtual machine and click on Settings
<li> Click the 'Network' tab
<li> 'Adapter 1' should be set to NAT by default (this allows you to get to the internet); click on 'Adapter 2' tab
<li> Click enable adapter and set attached to 'host only adapter'
</br>
[[File:selecting_host_only_adapter.png]]
</br>
<li> Start the virtual machine
<li> In your web browser, go to the url http://192.168.56.101/transfer/ (there is no need to login to the Archivematica virtual machine first). For ICA-AtoM, go to http://192.168.56.101/ica-atom/.
<li>Congratulations! You can now use both Archivematica and ICA-AtoM via your web browser.
</ol>

==Import files into virtual appliance (optional)==
If you want to use your own files in addition to the sample data provided, proceed with the following directions:

===Using SFTP===

It's possible to use [http://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol SSH File Transfer Protocol] (SFTP), through an [http://en.wikipedia.org/wiki/FTP_client FTP client] to upload your own content from your computer to the virtual desktop where Archivematica is running:

<ol>
<li> While in virtualbox right click the archivematica virtualmachine and click settings
<li> Click the 'Network' tab
<li> 'Adapter 1' should be set to NAT by default(this allows you to get to the internet), click on 'Adapter 2' tab
<li> Click enable adapter and set attached to 'host only adapter'
</br>
[[File:Selecting_host_only_adapter.png]]
</br>
<li> Power up the archivematica virtualmachine
<li> Once in the xubuntu interface goto Applications > Accessories > Terminal

<div class="note">
<strong>Having trouble locating the Applications menu?<strong></br>
You can find applications by clicking on the little blue logo in the top left-hand corner of the virtual desktop: [[File:applications_menu_icon.png]]. Alternately, you can access the terminal by simply right-clicking anywhere in the virtual desktop, and selecting "Open terminal here."
</div>

[[File:applications_accessories_terminal.png]]
</br>

<li> Type the following in terminal (the password is demo) - this will take a minute and requires internet
<pre>sudo aptitude install ssh </pre>

<div class="note"> <strong>Update packages?</strong></br>
If the terminal asks you to update and/or install new packages, do so. Hit "y" and return. </br>
[[File:package_updates.png]]</br>

</div>
</br>

<li> type "ifconfig" in the terminal. You should see an IP address like '192.168.56.101' (likely eth1 interface)
<pre>
$ ifconfig
eth1 Link encap:Ethernet HWaddr fe:54:00:9d:92:64
inet addr:192.168.56.101 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::1c6b:7bff:fe07:ddb6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1400 (1.4 KB) TX bytes:5815 (5.8 KB)
</pre>

</br>
<li> From here, your machine should be connectable via SFTP. Download an SFTP client; a popular open-source option is [http://filezilla-project.org/ FileZilla], which works on Linux and Windows. If you are using Apple's OSX or higher, [http://cyberduck.ch/ Cyberduck] is reported to be a decent open-source SFTP client.

</br>
<div class="note"> <strong>SFTP 101: Whats am I setting up here?</strong></br>
[http://en.wikipedia.org/wiki/File_Transfer_Protocol File Transfer Protoco]l (FTP) "is a standard network protocol used to transfer files from one host or to another host over a TCP-based network, such as the Internet" (Wikipedia). In this case, you will be using SFTP to transfer your files, which is an FTP protocol that uses a [http://en.wikipedia.org/wiki/Secure_Shell Secure Shell (SSH)] extension for more secure data transmission. When you use FizeZilla or Cyberduck, you are using an [http://en.wikipedia.org/wiki/Comparison_of_FTP_client_software FTP client]that provides a graphical user interface ([http://en.wikipedia.org/wiki/Graphical_user_interface GUI]) to allow you to move files easily from one host (in this case, your computer) to another (the virtual desktop).
</div>

<li> The connection information should be as follows
<pre>
username: demo
password: demo
IP/Hostname: 192.168.56.101 < results of ifconfig likely '192.168.56.*'
port: 22
destination folder: /home/demo/ < if this is not set you will have to navigate to /home/demo directory
</pre>
</br>
* Here is an example of setting up the connection information in <strong>FileZilla</strong>.

</br>
[[File:FileZilla_SFTP.png]]
</br>

* Note that the username, password, and host are all input into the top of the FileZilla browser.
* In FileZilla, your home computer's directory is displayed on the left hand side, while Archivematica's virtual appliance directory is on the right hand side. Once the connection is established, you can drag and drop content from one side to the other to upload content.
* If you require more support using FileZilla, please visit their documentation wiki [http://wiki.filezilla-project.org/Main_Page here].
* If you have dragged your content to the <strong>/home/demo </strong> folder, you can find your content in the Archivematica virtual appliance window by clicking on the "Home" icon on the desktop:
</br>
[[File:home_demo_filezilla.png]]
</br>
</br>
* Here is an example of setting up the connection information in <strong>Cyberduck</strong>:
[[File:CDconnect.png]]
*Cyberduck will only show one directory, so you may have to click on the Action button and select "Upload" to change the display and reveal Archivematica's directory.
[[File:CDhome-demo.png]]
*You will need to create a new folder inside an existing Media folder to upload your media files into. For example, double click on the arrow to open the "Pictures" folder and then create new folder in it and upload your digital images.
[[File:CDuploadfolder.png]]
*All further actions will occur in the <b>Archivematica dashboard</b> and instructions can be found in the User Manual under [https://www.archivematica.org/wiki/UM_transfer Transfer].
</br>

===Using Virtual Box Guest Additions===

#Run Jockey
#:<pre>sudo jockey-gtk</pre>
#Select Guest Additions from available drivers
#Restart

References
https://help.ubuntu.com/community/VirtualBox/SharedFolders
http://www.virtualbox.org/manual/ch04.html#sharedfolders

==Turn off virtual machine==
*At the end of your session, turn off the VirtualBox virtual machine by going to Machine > Close > and selecting one of the three shutdown options. It is best to choose either "Save the machine state" or "Send the shutdown signal". This is from the VirtualBox help manual:

<blockquote>3.4.3. Saving the state of the machine</blockquote>

<blockquote>When you click on the "Close" button of your virtual machine window (at the top right of the window, just like you would close any other window on your system) (or press the Host key together with "Q"), VirtualBox asks you whether you want to "save" or "power off" the VM.</blockquote>

<blockquote>The difference between these three options is crucial. They mean:</blockquote>

<blockquote>Save the machine state: With this option, VirtualBox "freezes" the virtual machine by completely saving its state to your local disk. When you later resume the VM (by again clicking the "Start" button in the VirtualBox main window), you will find that the VM continues exactly where it was left off. All your programs will still be open, and your computer resumes operation.</blockquote>

<blockquote>Saving the state of a virtual machine is thus in some ways similar to suspending a laptop computer (e.g. by closing its lid).</blockquote>

<blockquote>Send the shutdown signal. This will send an ACPI shutdown signal to the virtual machine, which has the same effect as if you had pressed the power button on a real computer. So long as a fairly modern operating system is installed and running in the VM, this should trigger a proper shutdown mechanism in the VM.</blockquote>

<blockquote>Power off the machine: With this option, VirtualBox also stops running the virtual machine, but without saving its state.</blockquote>

<blockquote>This is equivalent to pulling the power plug on a real computer without shutting it down properly. If you start the machine again after powering it off, your operating system will have to reboot completely and may begin a lengthy check of its (virtual) system disks.</blockquote>

<blockquote>As a result, this should not normally be done, since it can potentially cause data loss or an inconsistent state of the guest system on disk.</blockquote>

<blockquote>The "Discard" button in the main VirtualBox window discards a virtual machine's saved state. This has the same effect as powering it off, and the same warnings apply.</blockquote>

File:Qubit3g.png

2012-10-01T17:46:29Z

Dan: Dan uploaded a new version of "File:Qubit3g.png": Image changed to reflect AtoM 1.3

File:Qubit2g.png

2012-10-01T17:43:49Z

Dan: Dan uploaded a new version of "File:Qubit2g.png": Image updated to AtoM 1.3

File:Qubit-1g.png

2012-10-01T17:12:45Z

Dan: Dan uploaded a new version of "File:Qubit-1g.png": screenshot updated to AtoM 1.3

2012-09-17T20:51:11Z

Dan: /* Ubuntu login reset issue */

File:Archivematica virtualapp login.png

2012-09-17T20:24:05Z

Dan: The Archivematica login screen after setting it up to run as a virtual appliance on Oracle's Virtualbox.

The Archivematica login screen after setting it up to run as a virtual appliance on Oracle's Virtualbox.

File:Inside the VM.png

2012-09-17T20:22:18Z

Dan: An example of the first screen you will see when launching the Archivematica virtual appliance, after following the instructions on how to set up Oracle's Virtualbox.

An example of the first screen you will see when launching the Archivematica virtual appliance, after following the instructions on how to set up Oracle's Virtualbox.

Virtual appliance instructions

2012-09-17T20:21:20Z

Dan: /* Start Archivematica virtual appliance */

Virtual appliance instructions

2012-09-17T20:04:41Z

Dan: /* Start Archivematica virtual appliance */