<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="https://digitalcommons.library.arizona.edu/kb/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://digitalcommons.library.arizona.edu/kb/feed.php">
        <title> policy</title>
        <description></description>
        <link>https://digitalcommons.library.arizona.edu/kb/</link>
        <image rdf:resource="https://digitalcommons.library.arizona.edu/kb/lib/images/favicon.ico" />
       <dc:date>2009-08-08T09:03:37-07:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:for_administrators?rev=1226531308&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:for_depositors?rev=1226531327&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:for_developers?rev=1226531436&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:for_oai_harvesting?rev=1214766234&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:historical_accuracy_policy?rev=1226531218&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:home?rev=1214765721&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:preservation_policy?rev=1214766760&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:purposes?rev=1214766714&amp;do=diff"/>
                <rdf:li rdf:resource="https://digitalcommons.library.arizona.edu/kb/policy:security_and_access?rev=1226531186&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://digitalcommons.library.arizona.edu/kb/lib/images/favicon.ico">
        <title></title>
        <link>https://digitalcommons.library.arizona.edu/kb/</link>
        <url>https://digitalcommons.library.arizona.edu/kb/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:for_administrators?rev=1226531308&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-12T16:08:28-07:00</dc:date>
        <title>policy:for_administrators</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:for_administrators?rev=1226531308&amp;do=diff</link>
        <description>Information for administrators is currently being reviewed.  If immediate assistance is required, email UAiR.

Generally, administrators are assigned to collections, and at the moment (April 2008), administrative functions are provided directly through UAiR.  With our integration of Omeka, we are also evaluating how much of Omeka's administrative functionality will be implemented.  We like theirs better than ours, so it's likely that we're going to implement as much of Omeka's admin functionalit…</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:for_depositors?rev=1226531327&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-12T16:08:47-07:00</dc:date>
        <title>policy:for_depositors</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:for_depositors?rev=1226531327&amp;do=diff</link>
        <description>Information for depositors is currently being reviewed.  If immediate assistance is required, email UAiR.

Here's a list of some of our contemplations as of April 2008.

	*  Who can deposit? 
	*  By what means are we as an institution going to vet deposits? 
	*  What documentation is required for batch and single ingest?
	*  Do our depositors require specialized tool to help with metadata “creation?”
	*  How are we going to vet all the copyright issues?</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:for_developers?rev=1226531436&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-12T16:10:36-07:00</dc:date>
        <title>policy:for_developers</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:for_developers?rev=1226531436&amp;do=diff</link>
        <description>Our philosophy is simple.  We're going to create widgets and wonders once for the common use by many.  Our corollary philosophy is even more simple.  We're going to automate everything.  

As such, we will provide various means of publication, distribution, and harvesting of our metadata.</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:for_oai_harvesting?rev=1214766234&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-29T12:03:54-07:00</dc:date>
        <title>policy:for_oai_harvesting</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:for_oai_harvesting?rev=1214766234&amp;do=diff</link>
        <description>OAI AND HARVESTING


 
We are reviewing various methods to provide harvesting and federation functionality to everyone, not limiting harvesting to OAI-compatible systems.  As such, we are on track to implement RSS 2.0, ATOM 1.0, and SRU before the end of 2008.  Because of its limited functionality, we have chosen to postpone open release of OAI functionality until after the release of RSS and SRU.</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:historical_accuracy_policy?rev=1226531218&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-12T16:06:58-07:00</dc:date>
        <title>policy:historical_accuracy_policy</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:historical_accuracy_policy?rev=1226531218&amp;do=diff</link>
        <description>UAiR will present digital assets and digital collections as accurately as we can without editorial comment or device.

May 9, 2008</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:home?rev=1214765721&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-29T11:55:21-07:00</dc:date>
        <title>policy:home</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:home?rev=1214765721&amp;do=diff</link>
        <description>Policies and Guidelines of the Digital Commons

Policies

	*  Security and Access
	*  Historical Accuracy Policy
	*  Preservation Policy
	*  Purposes

Guidelines

	*  For Depositors
	*  For Administrators
	*  For Developers
	*  For OAI Harvesting</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:preservation_policy?rev=1214766760&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-29T12:12:40-07:00</dc:date>
        <title>policy:preservation_policy</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:preservation_policy?rev=1214766760&amp;do=diff</link>
        <description>Preservation Policy



 Implicit in the concept of an institutional repository is a commitment to long-term preservation and storage.  The repository is intended as a permanent, stable home for works of scholarship.  


 UAL IR Group, December 21, 2007

 Online May 14, 2008</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:purposes?rev=1214766714&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-29T12:11:54-07:00</dc:date>
        <title>policy:purposes</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:purposes?rev=1214766714&amp;do=diff</link>
        <description>The Purposes of an Insitutional Repository at the University of Arizona



 The following is an abbreviated list of the functions and purposes of the institutional repository at the University of Arizona.  

	*  Enable digital asset management
	*  Offer preservation services
	*  Provide digital visibility through access to collective intellectual work
	*  Support learning, teaching, and research
	*  Facilitate discovery of content
	*  Enable re-use and re-purposing of content
	*  Organize inform…</description>
    </item>
    <item rdf:about="https://digitalcommons.library.arizona.edu/kb/policy:security_and_access?rev=1226531186&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-12T16:06:26-07:00</dc:date>
        <title>policy:security_and_access</title>
        <link>https://digitalcommons.library.arizona.edu/kb/policy:security_and_access?rev=1226531186&amp;do=diff</link>
        <description>ACCESS

There are four possible levels of access in UAiR (as of 2008.04.30)

	*  Most assets (digital things) are available via open access.  The full public search should return assets that have attached metadata that fit your search request, regardless collection, point of origin, etc.  These objects are largely public domain, but users should check the Rights attached to the asset for any special provisions that might apply.  Attribution to UAiR or per the Rights statement should be given whe…</description>
    </item>
</rdf:RDF>
