{{headerMessage | translate: {id: item.handle} }}
{{descriptionMessage | translate}}
+ +
++ +
+{{'profile.head' | translate}}
{{'profile.groups.head' | translate}}
--
-
- {{ dsoNameService.getName(group) }} -
{{'profile.special.groups.head' | translate}}
--
-
- - {{ dsoNameService.getName(specialGroup) }} - -
{{ type + '.edit.head' | translate }}
+ + ++
Best practices for producing high + quality PDF files
+Version 1.0, 5 May 2006 +AdobeÕs Portable Document + Format (PDF) is a popular means of sharing documents, especially those + formatted for print. Not coincidentally, PDF files—when prepared + properly—also provide an excellent archival file format.
+The two most common ways + to create PDF files are with applications like Microsoft Word, + or by a scanning process that starts with printed materials. Below youÕll + find specific recommendations for producing high quality PDF files using + each of these methods.
+ ++ Windows instructions | + Macintosh instructions | + Scanning instructions | + More help +
+ +Creating + PDF files with applications supported by Adobe Acrobat on + a Windows platform
+You can create PDF files + from within Microsoft Word, for example, when you have the Adobe Acrobat + Standard or Acrobat Professional software. Note that Acrobat Standard + and Acrobat Professional are not the same as Acrobat Reader, the latter + being a free product with limited functions. When + configured properly, the resulting PDF files will be of high quality, suitable + for deposit.
+Use the following + steps to configure Adobe Acrobat and create PDF files from within a supported + application such as Microsoft Word.
+-
+
- Under
+ the Adobe PDF menu, select Change Conversion Settings. A new window will appear, as shown.
+
+
- At Conversion
+ Settings, select ÒPDF/A-1b:2005 (RGB)Ó and click Advanced Settings. A new window will
+ appear. In this window, click the Images folder and change
+ all three of the pixels per inch settings, as shown.
+
+
+
+
+ - Click OK. You will be prompted
+ to save the new settings. Enter ÒDeep Blue.joboptionsÓ and click Save as shown.
+
+
+
+
+ - Click OK. As shown, you will
+ now have a special Deep Blue conversion setting available whenever you
+ want to create PDF files for deposit.
+
+
+
+ - Now,
+ under the Adobe PDF menu, select Convert to Adobe PDF. You will be prompted
+ to save the PDF file, as shown.
+
+
+
+
+
+
+
+
Creating + PDF files with applications supported by Adobe Acrobat on a Macintosh platform
+As + per above, + you can produce high quality PDFs using the Adobe Acrobat Standard or Acrobat Professional software. Note + that Acrobat Standard and Acrobat Professional are not the same as Acrobat + Reader, the latter being a free product with limited functions.
+ +-
+
- In Acrobat, open Acrobat
+ Distiller via
+ the Advanced menu.
+ + - Under DistillerÕs Advanced menu item set the Default
+ Settings option to ÒPDF/A-1b:2005 (RGB)Ó.
+
+
+
+ + - Under DistillerÕs Edit menu, select Edit
+ Adobe PDF SettingsÉ A new
+ window will appear. In this window, click the Images tab
+ and change all three of the pixels per inch settings, as shown.
+
+
+
+ + - Click OK. You will be prompted
+ to save the new settings. Enter ÒDeep BlueÓ as shown.
+
+ +
+
+
+ - Click Save. As shown, you will
+ now have a special Deep Blue conversion setting available whenever you
+ want to create PDF files for deposit.
+
+
+
+ + - Now when you select PrintÉ in
+ Word, under the Printer: menu,
+ select ÒAdobe PDF 7.0Ó as shown below and then click the Print button. Note
+ that this is different from using the PDF option at the bottom of this
+ dialogue. Doing so will not produce
+ the results you want.
+
+
+
+
To create PDF files by scanning print materialÉ
+PDF files may also be + created by scanning print materials. From almost every perspective, all + of these methods are less preferable than creating PDF files directly from + an application as described above due to increased file size and compromised + viewing and printing characteristics. Nevertheless, PDF files created from + scanning are a reliable way to preserve materials when no other options + are available.
+Regardless of the method, + the produced PDF file should have the following properties:
+-
+
- All + materials should be scanned at 100% scale to the dimensions of the original. +
- Pages + containing text and/or line art should be monochrome (black and white), + 600dpi (or 300dpi for oversized materials greater than 11x16 in/28x41 cm), + and be compressed using ITU Group IV compression. +
- Pages + containing photographs and/or illustrations should be 24-bit color using + the sRGB color space or 8-bit grayscale, 400dpi (or 300dpi for oversized + materials greater than 11x16 in/28x41 cm), and be compressed with JPEG + compression using the highest quality setting. +
- Missing or blank pages + should be represented as blank images of the same size as the original. +
- The + PDF file should be optimized and should be in (ÒSearchable Image (Exact)Ó/ÒImage+TextÓ) + format. +
Éusing Adobe Acrobat Professional
+Adobe Acrobat Professional + has built-in scanning capabilities that can be used to create PDF files + using printed materials. Note that Acrobat Professional is not the same + as Acrobat Reader or Acrobat Standard; only Acrobat Professional has support + for scanning.
+Use the following steps + to create PDF files using a scanner with Adobe Acrobat Professional. These + steps apply to both Windows and Macintosh, with only slight variations + in appearance:
+-
+
- From the File menu, select Create + PDF and + then From Scanner. +
- Select your scanner + device, choose Front Sides or Both + Sides as appropriate, + select Recognize Text Using OCR, + and select Add Tags To Document. +
- Click Image Settings.
+ A new window will appear. In this window, change the settings as shown.
+
+
+
+
+ - Click Scan. +
Éusing your own choice of software
+Regardless of the method + you use, to create high-quality PDF files, follow the general guidelines + above as well as the following:
+-
+
- If your process creates + intermediate files (TIFF, PostScript, etc), it must not change the resolution + of the original scans (downsampling) or use lossy compression such as JPEG. + (These methods, although they do reduce file size, will cause irreversible + quality loss.) TIFF is an excellent choice for an intermediate file format, + and acceptable compression schemes (which can all be used in combination + with TIFF) are ITU Group 4 (for black and white material only), LZW, and + Flate (Zip). +
Creating + PDF files on a large scale
+If you need to create + a large number of PDF files, these approaches will not be efficient for + you, although the same principles outlined here will apply equally to a + large-volume operation. Before you start your project, contact us and we + will be happy to provide advice to your staff or to your scanning vendor + to make sure that your materials are in the best possible form for preservation.
+Questions?
+If + you have any questions, please contact us at DeepBlue and we will be happy + to help you create PDF files for the ages.
+
+
+ |
+
+ Author's Deposit Agreement
+ Version 1.0, 22 March 2005
+
I hereby grant + to the Regents of the University of Michigan the non-exclusive right to retain, + reproduce and distribute the deposited work (the Work) in whole or in part, + in and from its electronic format. This agreement does not represent a transfer + of copyright to the University of Michigan.
+The University + of Michigan may make and keep more than one copy of the Work for purposes + of security, backup, preservation and access, and may migrate the Work to + any medium or format for the purpose of preservation and access in the future. + The University of Michigan will not make any alteration, other than as allowed + by this agreement, to the Work.
+I represent + and warrant to the University of Michigan that the Work is my original work. + I also represent that the Work does not, to the best of my knowledge, infringe + or violate any rights of others.
+I further represent + and warrant that I have obtained all necessary rights to permit the University + of Michigan to reproduce and distribute the Work and that any third-party + owned content is clearly identified and acknowledged within the Work.
+By granting + this license, I acknowledge that I have read and agreed to the terms of this + agreement and all related Deep Blue and University of Michigan policies.
+ + + \ No newline at end of file diff --git a/src/assets/static/about/deepbluebatchagreement.html b/src/assets/static/about/deepbluebatchagreement.html new file mode 100644 index 00000000000..3db2aa4329b --- /dev/null +++ b/src/assets/static/about/deepbluebatchagreement.html @@ -0,0 +1,108 @@ + + + + + +
+
+ |
+
UM Institutional Repository
+Blanket Agreement for Batch Deposits
+ Author's Deposit Agreement
+ Version 1.2, 30 January 2006
+
This Agreement would be associated with + each deposit that is batch loaded by a designee (Community/Collection Coordinator), since + the batch load process bypasses the standard click-through license in the + submission workflow. It assumes that the designee, not the author, will do + batch loads.
+This Agreement is made by and between the [community name]____________ of + the University of Michigan (hereinafter called the Community), represented + by_____________, the Community's Collection Coordinator (hereinafter called the Designee) + and the University of Michigan Library's Deep Blue Institutional Repository + (hereinafter called the Repository) and is entered into on this ______day + of ________, 20__.
+This agreement allows the Designee to act + on behalf of individual depositors and/or the Community and authorizes the + Coordinator to batch load content to the Repository.
+On behalf of the Community, the Designee acknowledges having read all policies of the Repository and agrees to abide by the terms and conditions therein. + For content entrusted or gifted to the Designee, the Designee agrees that making the content available in the Repository is an appropriate and acceptable extension of its agreement with the Community, and is consistent with the Designee's charge to provide access to this content. + In addition, the Coordinator has conveyed to appropriate Community representatives the terms and conditions outlined in those policies, including the language of the standard deposit license quoted below and that the Community members have granted the Coordinator the authority to deposit content on their behalf.
+The standard deposit license states:
+I hereby grant to the Regents of the University + of Michigan the non-exclusive right to retain, reproduce and distribute the + deposited work (the Work) in whole or in part, in and from its electronic + format. This agreement does not represent a transfer of copyright to the University + of Michigan.
+The University of Michigan may make and keep + more than one copy of the Work for purposes of security, backup, preservation + and access, and may migrate the Work to any medium or format for the purpose + of preservation and access in the future. The University of Michigan will + not make any alteration, other than as allowed by this agreement, to the Work.
+I represent and warrant to the University + of Michigan that the Work is my original work. I also represent that the Work + does not, to the best of my knowledge, infringe or violate any rights of others.
+I further represent and warrant that I have + obtained all necessary rights to permit the University of Michigan to reproduce + and distribute the Work and that any third-party owned content is clearly + identified and acknowledged within the Work.
+By granting this license, I acknowledge that + I have read and agreed to the terms of this agreement and all related University + of Michigan and Deep Blue policies.
+This document will be stored in the Repository + attached to each deposit submitted by the Community.
+| Designee |
+ Repository |
+
| + | + |
| Signature: |
+ Signature: |
+
| Name: |
+ Name: |
+
| Title: |
+ Title: |
+
| Date: |
+ Date: |
+
| Email: |
+ Email: |
+
+
+ |
+
+ Click-Through Agreement: Designee Submitting on Behalf of Author
+ Version 1.1, 31 January 2006
+
This Agreement would be substituted for + the standard click-through license in a customized submission workflow where + we know that the Designee will be submitting content on behalf of Community + members.
+As the designated coordinator for this Deep + Blue Collection, I am authorized by the Community members to serve as their + representative in all dealings with the Repository. As the designee, I ensure + that I have read the Deep Blue policies. Furthermore, I have conveyed to the + community the terms and conditions outlined in those policies, including the + language of the standard deposit license quoted below and that the community + members have granted me the authority to deposit content on their behalf.
+The standard deposit licenses states:
+I hereby grant to the Regents of the University + of Michigan the non-exclusive right to retain, reproduce and distribute the + deposited work (the Work) in whole or in part, in and from its electronic + format. This agreement does not represent a transfer of copyright to the University + of Michigan.
+The University of Michigan may make and + keep more than one copy of the Work for purposes of security, backup, preservation + and access, and may migrate the Work to any medium or format for the purpose + of preservation and access in the future. The University of Michigan will + not make any alteration, other than as allowed by this agreement, to the Work.
+I represent and warrant to the University + of Michigan that the Work is my original work. I also represent that the Work + does not, to the best of my knowledge, infringe or violate any rights of others.
+I further represent and warrant that I + have obtained all necessary rights to permit the University of Michigan to + reproduce and distribute the Work and that any third-party owned content is + clearly identified and acknowledged within the Work.
+By + granting this license, I acknowledge that I have read and agreed to the terms + of this agreement and all related University of Michigan and Deep Blue policies.
+ + + + \ No newline at end of file diff --git a/src/assets/static/about/deepbluefaq.html b/src/assets/static/about/deepbluefaq.html new file mode 100644 index 00000000000..29a0f4649b0 --- /dev/null +++ b/src/assets/static/about/deepbluefaq.html @@ -0,0 +1,894 @@ + + + + +
+
+ |
+
+Deep Blue is the University of Michigan's permanent, safe, and +accessible service for representing our rich intellectual community +online. The primary goal of Deep Blue is to provide access to the work +that makes Michigan a leader in research, teaching, and creativity. By +representing our scholars, from faculty through students, as individuals +and as members of groups, Deep Blue provides a framework for preserving +and finding the best scholarly and artistic work done at the University.
+ ++What follows describes the types of works and collections the UM Library +envisions for Deep Blue, and how we gather, preserve, and offer access +to them. Because Deep Blue is designed to meet not only today's needs, +but also new needs as they evolve, this document is a work in progress. +Some aspects will undergo revision to reflect current needs and norms +identified by UM faculty, staff, students, and the collections they +create.
+ ++CONTENTS
+ + + + + + ++Preservation and Accessibility
+ ++ +
+Content and Collections
++ +
+What types of content can be deposited in Deep Blue?
+ ++We encourage the deposit of works with the following characteristics:
+ +-
+
- The work must be produced or sponsored by UM faculty, staff, students, +or UM academic and administrative research units with which our scholars are affiliated. +
- The work must be educational, artistic, or research-oriented. +
- The work must be a completed version, ready for distribution. +
- The author/owner must be willing and able to grant UM the non-exclusive right to preserve and distribute the work via Deep Blue. (See "What rights do I grant the University when I deposit my work in Deep Blue?"). +
- If the work is part of a series, we strongly encourage you to deposit +other works in that series so that Deep Blue can offer as complete a set as possible. +
+Examples of these works include:
+ +-
+
- Articles, preprints, working papers, technical reports, conference papers, web-based exhibits/presentations, etc. +
- Books +
- Theses +
- Data sets (scientific, demographic, GPS, etc.) +
- Computer programs +
- Visualizations, simulations, and other models +
- Multimedia +
- Learning objects (typically modular resources used in teaching, e.g. texts, syllabi, websites) +
+The Library has begun to populate Deep Blue with new and existing +digital works identified as having current and lasting value to the +campus. We will continue to do that, but our goal for Deep Blue is to +have decisions on what it should contain and offer be made mainly by you +and the other members of the UM community at large. So, we encourage you +to deposit your work and to contact us if you have format conversion +needs.
++ +
+Who can deposit items in Deep Blue?
+ ++Individuals can deposit items -- defined as individual +files/documents or related groups of files -- into collections and +collection administrators can create groups that can create new +collections and deposit items into collections. Example: A faculty +member giving a presentation at a conference can deposit the slides for +that presentation, the data behind the corresponding research, audio +and/or video clips supporting the research, a working paper about the +research, and so on, all as one package to be identified with a single +persistent URL to ensure reliable access.
+ ++We encourage the inclusion of excellent student work as well, though it +must be deposited through a UM faculty or staff member associated with +that work. This may happen directly (e.g., for Honors theses) or +indirectly in the case of officially recognized UM groups or +organizations with associated faculty sponsors (e.g., the UM Solar Car +Team). Ph.D. and Masters theses are a special case. Ph.D. theses are +handled through Rackham, and Masters theses are +handled by individual departments granting the degree. (Note that +depositing student work will require additional permissions from the +student in accordance with FERPA +regulations.)
+ ++To get started, contact the administrator of the collection you'd like +to add your work to, or contact Deep Blue.
++ +
+What are Deep Blue collections?
+ ++Deep Blue organizes its content around collections to +simplify the process of depositing your work and to provide you with the +most flexibility for finding work interesting to you. Schools, colleges, +departments, research institutes, and other large groups can +create collections in Deep Blue to group related works at the +broadest levels.
+ ++Collections allow people to explore a specific area in depth, or to +focus specifically on only the areas they find interesting. So, +collections contain the work of more focused/smaller groups and +individuals.
+ ++In the long term we hope to provide topical access that groups related +content together irrespective of who deposits it. With this structure in +place, you will be able to search or browse by collection, topic, +broader discipline, or type of work (e.g. theses and dissertations). As +we begin to offer searching across many universities and associate our +content with other Deep Blue equivalents at peer institutions, scholars +worldwide will have a rich and discipline-specific resource.
++ +
+Who can create new collections?
+ ++Individuals can create collections for depositing their +own work, and collection administrators can create groups that can build +collections together. For example, a faculty member can place +presentation material in her own collection. She can also administer and +create other collections that gather together the work of her research +group so all their presentations, datasets, etc. are browsable and +searchable as a subset of the University's works. Colleagues from other +universities are likely to find these groupings helpful for finding the +work that's most interesting to them. To get started, contact the +administrator of the collection to which you'd like to add your work to, +or contact Deep Blue.
++ +
+Who can become an administrator?
+ ++Each collection will have one or more administrator who will help the +Library define specific procedures that best suit its needs. This +administrator can be a faculty or staff member from a +school/college/etc., or can be a Library liaison to that school/college. +We are happy to help you set up collections and work with you to set up +access, membership, and other parameters. The collection structure is +intended to be flexible and adaptable to the needs of individuals and +their colleagues, and the Library commits to making Deep Blue responsive +to the changing needs and nature of the creative, intellectual, and +artistic work done here. Please contact Deep Blue to get started.
+ ++For more information about community responsibilities, see Roles and Responsibilities of Deep Blue +Partners.
++ +
+Intellectual Property Rights
++ +
+Honoring your rights as a creator is a fundamental aspect of Deep Blue's +support of your work and the University's mission of creating knowledge. +The service's deposit agreements, policies, and principles ensure that +you retain all your intellectual property rights when depositing your +work.
+ ++Deep Blue also supports the University's mission of communicating the +knowledge created here to the citizens of Michigan and the world, and +does so by offering a service geared towards providing the broadest +possible access to our creative, intellectual, and artistic work. We +encourage you to explore all means of allowing others to build upon your +work. For example, we offer use of the "Creative Commons" +license as a supported option for your collection.
+ ++Because the topic of intellectual property has specific legal +implications, Deep Blue has a formal policy. It has four parts:
+ +-
+
- a Deep Blue Intellectual Property +Policy that formally addresses the concepts outlined +below; +
- an Author's Deposit Agreement (see below) used by an +author/creator depositing his or her own work; +
- a Collection Coordinator Agreement, used by a designated +coordinator (such as a departmental administrator or secretary, or a +library liaison), and; +
- a Blanket Agreement for Batch Deposits used when an +author/creator or designated coordinator deposits batches/groups of +work. +
+ +
+What rights do I grant the University when I +deposit my work in Deep Blue?
+ ++When you agree to our standard "Author's Deposit Agreement" (see below) +at the time of deposit you grant Deep Blue the non-exclusive right to:
+ +-
+
- retain, reproduce, and distribute the deposited work; +
- keep more than one copy of your work for purposes of security, backup, +preservation, and access, and; +
- migrate your work to any future medium or format for the purpose of +preservation and access. +
+The "Author's Deposit Agreement". + +
+ +
The deposit agreement mentions "original work." What does that mean?
+ ++In most cases it's obvious when a work is original to you, especially +when you are its sole creator. Other examples of original work that you +may deposit include:
+ +-
+
- Annotated or illustrated versions of public domain works. For example, +if a UM mathematics lecturer added annotations to Alice in +Wonderland or an art professor illustrated Moby Dick, both +have created a new original work and we would encourage them to deposit +the digital versions of those works in Deep Blue. +
- Works which you co-authored, such as reports on research done +with colleagues at UM or elsewhere. Unless you grant specific rights +(such as the right to distribute) to someone else, the intellectual +property is owned equally and in full by all creators. +
+Related to that, in the third and fourth paragraph of the agreement, you +represent that you have the right to make the deposit and that you're +not infringing on the rights of others by doing so. If you have +questions about the status of your work, a number of resources exist on +campus to assist you, including "Copyrights at the +University of Michigan".
++ +
What rights do I retain?
+ ++You retain all your intellectual property rights. The +limited rights you grant to Deep Blue are non-exclusive, and your +ability to grant, assign, or retain any and all rights you had before +your deposit does not change as a result of your deposit. Please note +that some publishers may ask that you grant them exclusive rights to +your work, thus limiting your ability to use it as you see fit and +perhaps even limiting your ability to deposit it in Deep Blue.
++ +
+Who Can Use Deep Blue
++ +
+Who can search, browse, and download from Deep Blue?
+ ++Deep Blue is designed to provide your work the widest possible exposure, +so it is open to the world for searching. You may, however, choose to +deposit your work but prevent it from being seen in full for a limited +time. You may also choose to allow people to find out about the +existence of your work, but not download the work itself, again for a +limited time. See "Can I restrict access to +the item I deposited?" below for more details.
++ +
+What conditions of use does Deep Blue grant people for my +deposit?
+ ++As a depositor, you control the conditions of use for your +work. Depositing your work in Deep Blue does not affect your +copyright, so you retain all the rights you had before making it +available through this service. You are only granting UM the +non-exclusive right to distribute the work. See the section on Intellectual Property Rights for more +information about rights, limitations of use, and suggestions for making +sure your work is accessible the way you want it to be.
++ +
+I just found some interesting work done by someone else in Deep +Blue and am about to download it -- what can I do with that work once I +have it?
+ ++Directly above you'll see that depositors -- typically the +creators/authors -- control the rights to their work. Unless +otherwise noted in Deep Blue or on the work itself, you should treat the +work like any other copyrighted material, and may make "Fair Use" of it as allowed by law.
++ +
+Can I restrict access to the item I +deposited? If so, to whom, and for how long?
+ ++Yes. Since the work you deposit is complete and ready for distribution +(see "What types of deposits do we encourage?"), immediate and +worldwide access is the default (and preferred) status for all material +in Deep Blue. But we know situations exist where you won't want to offer +immediate access. So, legal requirements the University is bound to +honor (such as FOIA requests) notwithstanding, you can limit access to +items in Deep Blue collections for a period of time defined by the +community or collection into which you're depositing your work.
+ ++For example, you can limit access to an item to only people from your +research group or department for a period of time after you deposit it. +That way everyone from your team/department can find your work and use +it, while those outside cannot. This limitation can be extended to the +full metadata as well. This limited "embargo period," agreed on by the e +collection's administrator(s) and Deep Blue staff, will determine when +the full description and the item itself will become accessible to the +UM community -- and later the world -- at large. Standard embargo +periods are:
+ +-
+
- Immediate access to full description and all files (the default) +
- Access to full description and all files in 3 months +
- Access to full description and all files in 6 months +
- Access to full description and all files in 1 year +
+You can also limit access to an item to people on the UM campus. This +limitation does not extend to the descriptive metadata -- those outside +will be able to find out about the item when they search Deep Blue. Here +again, a limited embargo period can be applied to worldwide access to +the item itself.
+ ++Your collection administrator, together with the Deep Blue staff at the +Library, define the embargo options offered on your deposit form. +Contact your collection administrator if you have questions.
++ +
+Depositing Your Work
++ +
+What do I have to do to deposit work?
+ ++For UM faculty and staff, the first step is to either identify a +collection to work with, or to create one. (The process is different if +you are a student. See "Who can deposit +items in Deep Blue?" above for more information.) We encourage +you to browse Deep Blue and then contact Library +staff at Deep Blue who will assist you in contacting the right +collection administrators to gain permission to deposit your work. We +can also help you create a collection if that's more appropriate.
++ +
+What descriptive information do I assign to the work at time of deposit?
+ ++To provide searchability beyond simply the full text, depositors must +provide:
+ +-
+
- Title +
- Creator/Owner (typically this is also the Author) +
- Date of publication/creation/issue +
+We encourage you to provide more complete descriptive information -- +also known as metadata -- by filling out as many fields on the deposit +form as possible. This will allow Deep Blue to offer more ways of +finding and retrieving the work based on your special knowledge of its +contents. If you would like to customize your collection's interface so +you can ensure more than Deep Blue's minimum metadata are required, +please contact Deep Blue.
++ +
+Will the Library enhance my deposit by, for example, adding +additional metadata?
+ ++Deep Blue is intended to reflect the campus and its scholarly activity, +and to make the work done here accessible as promptly as possible. When +the Library finds that we can improve access by enhancing the +information about a deposited item we will do our best to make those +enhancements. If you wish to have us do this for items you deposit, +please contact Deep Blue and we will be glad to discuss how best to accomplish it and +whether any costs will be involved.
+ ++Works that include raw data (such as social science datasets, GIS files) +are noteworthy in that metadata for them needs to be far more detailed +than for other items since author, title or even a full-text search will +typically not help someone new to the material determine whether those +data are of interest. Please contact us at the time of deposit so we can +assist you in describing them more fully.
++ +
+When depositing items, can I insert superscripts, subscripts, and other special characters in titles, abstracts, etc.?
+ ++Yes, although doing so is not as simple as cutting/pasting from a +typical word processor document. You need to do a little extra work, and +use a UTF-8 or -16 font; 'Arial' is a good choice for Roman characters, +and one that you can commonly find on a PC or Macintosh.
+ ++To insert special characters, in Microsoft Windows XP you use the +Character Map program (START/Programs/Utilities/Character Map). On a +Macintosh, you use the Character Palette (under the flag icon showing +your keyboard type in the upper right hand of the screen). Pick a UTF-8 +or -16 font from the Map/Palette and you'll notice that in these fonts a +superscript 2 is a separate character from a 2 upon which you might +apply e.g. Microsoft Word's character formatting. So to enter a title +into Deep Blue, you would first copy and paste the title from your word +processing document into a new one. Then:
+ +-
+
- Identify every special character (superscripts, subscripts, +symbols, non-Roman characters, etc.) and find them in the Character +Map/Palette. +
- Drag and drop the special character from the Map/Palette into the +appropriate place, and delete the version that you made via the word processor's +formatting option. +
- Repeat these two steps until you've recreated the whole title. +
+Then, copy and paste this title into the appropriate field on your Deep +Blue form. Though this sounds complex, it's actually harder to describe +than it is to do. If you have any questions, please contact Deep Blue.
++ +
+Will the Library enhance my deposit in other ways?
+ ++When the Library determines we can improve access by providing a new +context for the work (such as representing the work in additional +collections beyond the one you deposited it in) or better preserve your +work by changing its format, we will do so.
++ +
+Does Deep Blue assign any metadata automatically?
+ ++At the time of deposit Deep Blue automatically assigns
+ +-
+
- Persistent URL for you and others to cite +
- Deposit Date +
- Depositor's Name +
- File Format (based on its extension) +
+This information is used to manage content over time.
+ ++If you would like to further customize your collection interface to add +more information automatically, please contact Deep Blue.
++ +
+If I don't want to assign a lot of descriptive metadata to my deposit, +will the Library do it for me?
+ ++Yes. The Library will assign additional metadata whenever it can do so. +For example, we can help you add the Michigan Metadata in use by BlueStream +and other projects, or connect you with a cataloger who can help you +better describe your content.
+ ++Assigning metadata can be time-consuming and therefore costly, so if you +need help from the Library, please contact Deep Blue and we will work with you to reach an agreement on how to +accomplish this most effectively.
++ +
+Can I deposit content in any format?
+ ++Our goal of providing access to your work means that Deep Blue accepts +all digital formats. However, not all formats can receive the same level +of preservation support.
+ ++For more detailed information about format support, see the Preservation and Accessibility +section.
++ +
+What types of deposits does the Library discourage?
+ ++The guidelines above are inclusive, and purposely so, as we hope to have +Deep Blue represent the UM intellectual environment as broadly as +possible. Deciding what should be included in Deep Blue is largely the +function of the individual depositors and the collections with which +they're affiliated. Individuals and collection administrators may wish +to work closely with their Library liaisons and may decide it's more +efficient and convenient to delegate some of the deposit decisions to +them.
+ ++While there may be cases where the Library will need to discuss deposits +with you, or even remove a deposit, we anticipate these cases will be +rare. There are however some items that you may not be able to deposit +or that may find a better home, either temporarily or permanently, +elsewhere at UM. Two examples of the latter:
+ +-
+
- Works in progress will typically be better served via personal websites, +departmental servers, in Blue Stream or perhaps via CTools, all of which +provide tools and platforms for modifying and completing work to make it +ready for distribution. +
- Per the Standard Practice Guide, some completed materials, +especially those of an administrative nature, are better suited for +the University Archives at the Bentley Historical Library. +
+Deep Blue may in exceptional cases decline a submission due to technical +challenges or out-of-scope content. If you have questions please contact Deep Blue and we will be glad to help you determine the best place for +your item(s).
++ + +
+What type of already existing materials can I add to Deep Blue?
+ ++Deep Blue will focus on new digital materials, and the Library will also +experiment with making some of its large digital collections of UM-based +work available as well.
+ ++That said, we encourage collection administrators and individuals +(including Library selectors and departmental liaisons) to continue to +identify excellent but less current materials, both in digital and +non-digital form. UM has produced a tremendous amount of interesting +work, and that will require prioritization, especially when that work +must be digitized to make it available through Deep Blue. Please contact Deep Blue if you have items like this and we will work with you to make +them available.
++ +
+How large a deposit can I make?
+ ++The size of an item does not matter as such. There are practical +limitations, though, especially where video, large datasets and similar +items are concerned. Because of network constraints, depositing files +larger than 250 Mb will probably require the assistance of the Library, +which can provide better means for reliably depositing them. (For +instance, we will want to compare checksums on your file before and +after deposit to verify that the file transferred correctly and +completely.) We will handle these on a case-by-case basis, so please +contact contact Deep Blue if you plan to deposit large files.
++ +
+Can I withdraw a deposit?
+ ++Yes. Deep Blue is designed to provide long-term, permanent access to the +items you deposit. However, we know circumstances can arise where a +deposit will need to be removed from view. When this becomes necessary, +contact your collection administrator and together we will determine the +best course of action to take.
+ ++However, since any item in Deep Blue may have been cited via its +persistent URL, we will always supply a "tombstone" whenever the item is +requested. The tombstone will contain the metadata for the item, with +one of the following messages indicating why the item was removed:
+ +-
+
- "Removed from view by legal order." +
- "Removed from view by the University of Michigan." +
- "Removed from view at request of the author." +
+The tombstone metadata will be visible to those who already have its +persistent URL, but your deposit and its metadata will no longer be +searchable and we will make these items unavailable for harvesting by +services such as OAIster and Google.
++ +
+Can I remove a file from an existing deposit?
+ ++Though it is possible under certain circumstances, to preserve the historical record of your scholarship, and +because others may have cited the old version, the preferred way to +handle this is to clearly mark the old, out-of-date version as +"Superceded" in both the 'Description' field for the file and add a +coversheet (or its equivalent) to the file itself. Contact your +collection administrator for help with this.
++ +
+User Support Services
++ +
+Deep Blue's basic services provide a system that allows Deep Blue +depositors and administrators to deposit their work and all users to +access items in Deep Blue. Management services provide ongoing support +for creating new and enhancing existing Deep Blue communities, +responding to customer inquiries, and supplying system monitoring, +back-up, and recovery. We are investigating services beyond these which +may be offered for a fee.
+ ++The Library commits to the Deep Blue Deposit Services (for already +authorized users) and Access Services (for all), as defined in Deep Blue Services on a 24x7 basis. +Deep Blue Management Services, supporting collection set-up and related +tasks as defined in "Deep Blue Services" are provided Monday +through Friday, 9:00am to 5:00pm.
++ +
+I'm trying to access Deep Blue and am getting system errors/no +response. Who should I report this to?
+ ++If you are trying to search/browse Deep Blue and it is not responding, +please contact Deep Blue to report the outage.
++ +
+I'm trying to deposit my work in Deep Blue, but even though I'm an +authorized user and can log in I can't do so now. Who should I report +this to?
+ ++Please contact Deep Blue to report the outage.
++ +
+How can I get more help with Management Services?
+ ++The Library will provide both web-based/email and telephone support to +all Deep Blue users. Support will be provided Monday through Friday, +9:00am to 5:00pm. All inquiries will receive a return response via +e-mail or telephone within one business day.
+ + + +or
+ +763-4835
+ ++Library liaisons and subject specialists also work with the Deep Blue +coordinator and Systems Administrator to provide of End-User Support +Services, with back-up from the Digital Library Production Services and +Core Services staff. For a complete definition of services see Deep Blue Services.
++ +
Preservation and Accessibility
++ +
+Deep Blue is committed to providing long-term access to every deposit +you make. At the same time, while the Library has a long history and +many years of experience in the area of preservation, we recognize that +both the digital landscape and our understanding of the complexities of +digital preservation continue to evolve. We anticipate that over time +both the public and private sectors will develop more tools and +techniques to facilitate long-term preservation of digital information, +so these preservation principles and policies will continue to +evolve.
+ ++For more specific information about our commitment to preservation, see +the Deep Blue Preservation and Format +Support Policy.
++ +
+Can you explain the different levels of format support you provide +for my work?
+ ++You may deposit work in any digital format in Deep Blue, but not all +formats can receive the same level of preservation commitment. Deep Blue +has designated three levels of support we can offer, based on criteria +such as the wide deployment of the format, availability of +publicly-documented specifications, and the expectation that tools will +be available to undertake controlled transformation or migration. They +are described in detail in the Deep Blue Preservation and Format +Support Policy.
+ ++TIFF (.tiff, .tif) is an example of a "Level 1" type of format. Widely +used and an open standard, we can support it to our fullest extent. An +example of a "Level 2" format is an MS Word document (.doc). Because +Microsoft owns and controls the specifications for this format, but +doesn't publish them, some features like macros may not operate between +versions regardless of our best efforts. Windows Media Audio (.wma), +because of its close ties to a specific platform and because it is far +less common than MP3 or WAV formats, serves as a good example of a +"Level 3" format that we can only commit to preserving at the bit level. +In other words, in the future you will be able to download an exact copy +of the deposited file, but it may be difficult to open and use it +without legacy hardware and/or software.
++ +
+What other preservation services does Deep Blue provide?
+ ++For all content you deposit, Deep Blue will provide secure storage, +backup, management, fixity-checks, and periodic refreshment by copying +the data to new storage media. We will also undertake appropriate format +monitoring and provide adequate staffing and other resources to support +the services offered. In addition, Deep Blue staff is developing +best-practice guidelines to help depositors convert or create documents +that achieve the level of quality needed for information capture and the +highest degree of preservability over time. +Further, we make the following commitments to preservation:
+ +-
+
- Deep Blue provides a persistent URL (we use "handles" that will +always point to either the deposited item or its metadata. +
- The Library will maintain that persistent URL, and the +files/metadata associated with it. +
+ +
+What formats receive the Highest Level (Level 1) of +preservation?
+ ++For a list of all recognized Deep Blue formats and their current support +levels, see the Deep Blue +Preservation and Format Support Policy. We expect to add to and +revise the support levels as standards emerge for digital preservation +of additional formats.
++ +
+Why isn't PDF considered a Level 1 format? What is PDF/A?
+ ++Adobe's Portable Document Format (PDF), as you currently generate it +using most commercial applications on your computer, is a proprietary +format owned and controlled by Adobe Systems, Inc. So despite its wide +use, it is not publicly documented at this time. An international +preservation standard for PDF/A -- "ISO 19005-1 for PDF/A-1," where the +"A" stands for archive -- exists. We have developed guidelines for +creating PDFs to which we can apply our highest level (Level 1) of +preservation support. Please contact Deep Blue for more information.
++ +
+Can you preserve all the relationships in items made up of multiple files?
+ ++At present, the three levels of preservation commitment are made at the +individual file level. We will need to evaluate complex content -- items +comprised of files in various formats that interact with each other -- +to determine whether the operational relationships between the files can +be maintained. Executables and some files that rely on a specific +hardware/software environment will also require additional evaluation +because not only the format but the access environment must be +considered in determining preservation issues. Please contact the Deep Blue Preservation Group if you wish to deposit any of these content +types.
++ +
+How accessible are Deep Blue documents for people with disabilities?
+ ++Deep Blue accepts many formats and places few restrictions on depositors. +As such, the files found here may vary in their accessibility features and +their usability for people with disabilities. We encourage all depositors +to make their work as accessible as possible, since this ensures ease of use + and the broadest possible readership for their work.
+ ++ If you are unable to use a specific file in its current format, please select + the Contact Us + link and we can modify it to make it more accessible to you. +
+ ++Since many of the items in Deep Blue are in PDF format, we have created + guidelines for creating high quality, +accessible PDFs.
+ ++There are many applications that offer more robust capabilities that support +a variety of file formats. On the U-M Ann Arbor campus, you can get assistance +installing and using them via the + +Adaptive Software and Hardware site , U-M +Office of Services for Students with Disabilities , and + Library Accessibility +Services .
+ ++ +
Privacy
+ +You can find Deep Blue's privacy policy here. + + + \ No newline at end of file diff --git a/src/assets/static/about/deepblueformatlevels.html b/src/assets/static/about/deepblueformatlevels.html new file mode 100644 index 00000000000..2ba81383769 --- /dev/null +++ b/src/assets/static/about/deepblueformatlevels.html @@ -0,0 +1,25 @@ + + +
+ + + + + + + +-
+
- Highest Level (Level 1): The highest level of preservation support. We will make our best effort + to maintain all the content, structure and functionality of the work + you deposit by taking appropriate preservation actions over time. +
- Limited (Level 2): Limited preservation + support. We will preserve the content of the deposit, but its appearance + and functionality may not be preservable over time. +
- As-is (Level 3):We preserve your deposit "as-is". This is commonly called bit-level preservation, + where the work is preserved exactly as you deposited it in Deep Blue. +
| Feature |
+ Level 1 |
+ Level 2 |
+ Level 3 |
+
| Persistent identifier that will always point to the object and/or its metadata |
+ • |
+ • |
+ • |
+
| Provenance records and other preservation metadata to support accessibility and management over time |
+ • |
+ • |
+ • |
+
| Secure storage and backup |
+ • |
+ • |
+ • |
+
| Periodic refreshment to new storage media |
+ • |
+ • |
+ • |
+
| Fixity checks using proven checksum methods |
+ • |
+ • |
+ • |
+
| Storage in a trusted preservable format (making a normalized version, if necessary) |
+ • |
+ for some formats |
+ + |
| Strategic monitoring of format |
+ • |
+ • |
+ + |
| Migration to succeeding format upon obsolescence |
+ • |
+ + | + |
+
+ |
+
UM Institutional Repository
+ Intellectual Property Policy
+ Version 1.0, 22 March 2005
+
+ Deep Blue, the University of Michigan Institutional Repository (referred + to hereafter as the Repository), is a service of the University of Michigan + Library, provided to lower access barriers and offer the widest possible dissemination + for the intellectual and creative output of the University. The Repository + also provides appropriate long-term preservation services for that content + to ensure continuing access over time. Content is made available through a + non-exclusive license granted by the author; there is no transfer of intellectual + property rights accompanying submission of content to the Repository.
+-
+
- Author's Deposit Agreement +
- Agreement for Designee Submitting on Behalf of Author +
- Blanket Agreement for Batch Deposits +
The authors or + their designees grant to the Repository a non-exclusive right to:
+-
+
- display and distribute the submission including its abstract and descriptive + information in electronic format in accordance with the Repository's policies +
- copy, convert or migrate the submission + to any medium or format for the purpose of preservation and access +
- keep more than one copy of the submission + for purposes of security, back-up, and preservation +
When depositing a Work, depositors or their designees should represent the + Work's copyright status in a manner consistent with the University's copyright + policy, Ownership Of Copyrighted Works Created At Or In Affiliation With + The University Of Michigan (June 6, 2002, approved by the Regents on November + 14, 2002). The Repository is committed to open access and prefers that content + be deposited without access restriction. However, it will make reasonable + efforts to limit access to authorized Michigan users or specific users, if + restrictions are associated with a submission at the time of deposit.
+ +The Repository will work with the depositor or their designee to allow submissions + to be added to, replaced or removed, to comply with subsequent changes to + an item's access policy or to reflect a revision to the work. In the event + a published submission is replaced or removed, the Repository will retain + a descriptive record for citation purposes.
+ +Although the + depositor or their designee has the right to remove content from the Repository, + we recommend that material be deposited in perpetuity, to ensure continuity + of access and citation and to facilitate long-term preservation.
+In addition, + the depositor or their designee grants to the Repository the right to:
+-
+
- share the descriptive information and + abstract for the submission in a variety of settings to encourage access +
- enhance descriptive information about + the submission to support access +
The Repository + shall obtain express written permission from the author or their designee + to use the content for any commercial purpose.
+In the event + of the dissolution of a research group, center, institute, or any other unit + that is represented in the Repository, content will continue to be held by + the Repository unless individual copyright holders request removal or access + restriction.
+In the case of + joint authorship, if the individual copyright holders disagree on whether + or how their Work is represented in the Repository, content will continue + to be held by the Repository in the manner in which it existed at the time + of the disagreement until the copyright holders jointly request a change to + that status.
+Content deemed + to be official University records may be transferred to the control of the + University Archives while remaining in the Repository.
+ + + \ No newline at end of file diff --git a/src/assets/static/about/deepblueknownformats.html b/src/assets/static/about/deepblueknownformats.html new file mode 100644 index 00000000000..3cf342f4e88 --- /dev/null +++ b/src/assets/static/about/deepblueknownformats.html @@ -0,0 +1,875 @@ + + + + + + + +Registered Formats and Support Levels
+ +This list of formats and support levels will be regularly reviewed and + update based on our growing experience with digital preservation and the +emergence of new formats and standards.
+ ++ +
Last updated March 9, 2011
+ ++ +
|
+ TEXT AND PAGE DESCRIPTION FORMATS (Best Practices For Creating Quality PDFs) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ PDF/A + |
+
+ |
+
+ application/pdf + |
+
+ Level 1 + |
+
+ Best Practices
+ |
+
|
+ Plain Text UTF-8 (Unicode) + |
+
+ .txt + |
+
+ text/plain; charset=UTF-8 + |
+
+ Level 1 + |
+
+ + |
+
|
+ Plain Text ANSI X3.4/ECMA-6/US-ASCII (7-bit) + |
+
+ .txt + |
+
+ text/plain; charset=US-ASCII + |
+
+ Level 1 + |
+
+ + |
+
|
+ SGML + |
+
+ .sgm, .sgml + |
+
+ application/sgml + |
+
+ Level 1 + |
+
+ Requires that DTD is deposited with SGML file and that SGML file parses against it + |
+
|
+ XML + |
+
+ .xml + |
+
+ text/xml + |
+
+ Level 1 /
+ |
+
+ Level 1 requires that DTD/schema is deposited with XML file and that XML file parses against it; Level 2 assumes no DTD/schema but that XML file is well-formed + |
+
|
+ HTML + |
+
+ .html, .htm + |
+
+ text/html + |
+
+ Level 2 + |
+
+ Requires HTML 4.0 or 4.01 validated markup and CSS files(s), if referenced, be deposited with document + |
+
|
+ LaTeX + |
+
+ .latex + |
+
+ application/x-latex + |
+
+ Level 2 /
+ |
+
+ Level 2 requires that referenced style files and/or embedded items be deposited with document + |
+
|
+ Postscript + |
+
+ .ps + |
+
+ application/ps + |
+
+ Level 2 + |
+
+ + |
+
|
+ Rich Text + |
+
+ .rtf + |
+
+ text/richtext + |
+
+ Level 2 + |
+
+ + |
+
|
+ TeX + |
+
+ .tex + |
+
+ application/x-tex + |
+
+ Level 2 /
+ |
+
+ Level 2 requires that referenced style files and/or embedded items be deposited with document + |
+
|
+ Plain Text ISO 8859-x
+ |
+
+ .txt + |
+
+ text/plain; charset=ISO-8859-x + |
+
+ Level 2 + |
+
+ + |
+
|
+ Plain Text; |
+
+ .txt + |
+
+ text/plain + |
+
+ Level 3 + |
+
+ + |
+
+ +
|
+ COMMON DESKTOP SOFTWARE FORMATS (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ Microsoft Word + |
+
+ .doc + |
+
+ application/msword + |
+
+ Level 2 + |
+
+ Requires that macros be disabled + |
+
|
+ Microsoft PowerPoint + |
+
+ .ppt + |
+
+ application/ |
+
+ Level 2 + |
+
+ Requires that macros, animation and other effects be disabled + |
+
|
+ Microsoft Excel + |
+
+ .xls + |
+
+ application/vnd.ms-excel + |
+
+ Level 2 + |
+
+ Requires that macros be disabled. (See also Best Practices for Datasets) + |
+
+ +
|
+ IMAGE FILE FORMATS (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ JPEG + |
+
+ .jpg + |
+
+ image/jpeg + |
+
+ Level 1 + |
+
+ + |
+
|
+ TIFF + |
+
+ .tiff + |
+
+ image/tiff + |
+
+ Level 1 + |
+
+ + |
+
|
+ JPEG 2000 + |
+
+ + |
+
+ + |
+
+ Level 2 + |
+
+ Level 1 support expected as more tools become available + |
+
|
+ PNG + |
+
+ .png + |
+
+ image/png + |
+
+ Level 2 + |
+
+ + |
+
|
+ BMP + |
+
+ .bmp + |
+
+ image/x-ms-bmp + |
+
+ Level 3 + |
+
+ + |
+
|
+ GIF + |
+
+ .gif + |
+
+ image/gif + |
+
+ Level 3 + |
+
+ + |
+
|
+ Photo CD + |
+
+ .pcd + |
+
+ image/x-photo-cd + |
+
+ Level 3 + |
+
+ + |
+
|
+ Photoshop + |
+
+ .psd + |
+
+ application/x-photoshop + |
+
+ Level 3 + |
+
+ + |
+
+ +
|
+ AUDIO (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ AIFF + |
+
+ .aif, .aiff + |
+
+ audio/aiff, + + |
+
+ Level 1 + |
+
+ + |
+
|
+ Wave + |
+
+ .wav + |
+
+ audio/x-wav or audio/wav + |
+
+ Level 1 + |
+
+ + |
+
|
+ Audio/Basic + |
+
+ .au, .snd + |
+
+ audio/basic + |
+
+ Level 2 + |
+
+ + |
+
|
+ MPEG audio + |
+
+ .mp3 + |
+
+ audio/mpeg, audio/mp3 + |
+
+ Level 2 + |
+
+ + |
+
|
+ AAC_M4A + |
+
+ m4a, .mp4 + |
+
+ audio/m4a, audio/mp4 + |
+
+ Level 2 + |
+
+ + |
+
|
+ Real Audio + |
+
+ .ra, .rm, .ram + |
+
+ audio/vnd.rn-realaudio + |
+
+ Level 3 + |
+
+ + |
+
|
+ Windows Media Audio + |
+
+ .wma + |
+
+ audio/x-ms-wma + |
+
+ Level 3 + |
+
+ + |
+
+ +
|
+ VIDEO (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ AVI + |
+
+ .avi + |
+
+ video/avi, video/msvideo, video/x-msvideo + + |
+
+ Level 2 + |
+
+ + |
+
|
+ Quicktime + |
+
+ .mov + |
+
+ video/quicktime, video/x-quicktime + |
+
+ Level 2 + |
+
+ + |
+
|
+ MPEG-1 |
+
+ .mp1 |
+
+ video/mpeg |
+
+ Level 2 + |
+
+ Many variants possible; preservation level not yet established + |
+
|
+ MPEG-4 + |
+
+ .mp4 + |
+
+ video/mp4 + |
+
+ Level 2 + |
+
+ Many variants possible; preservation level not yet established + |
+
|
+ Windows Media Video + |
+
+ .wmv + |
+
+ video/x-ms-wmv + |
+
+ Level 3 + |
+
+ + |
+
+ + +
|
+ OTHER/MISCELLANEOUS + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ ZIP/tar + |
+
+ .zip, .gz, tar.gz + |
+
+ application/zip; application/x-gzip + |
+
+ Level 1; see "Qualifying Factors/Notes" + |
+
+ ZIP or tar files are only as good as their contents; all best practices above still apply. (See also Best practices for producing ZIP and tar files) + |
+
+ + + + \ No newline at end of file diff --git a/src/assets/static/about/deepblueleveloneformats.html b/src/assets/static/about/deepblueleveloneformats.html new file mode 100644 index 00000000000..8de3bc6df0c --- /dev/null +++ b/src/assets/static/about/deepblueleveloneformats.html @@ -0,0 +1,26 @@ + + + + + + + + +
-
+
- Text (.txt) in UTF-8, ANSI X3.4/ECMA-6/US-ASCII +
- XML (.xml) text/xml +
- SGML (.sgm, .sgml) application/sgml +
- PDF/A (.pdf) application/pdf +
- TIFF (.tif, .tiff) image/tiff +
- JPEG (.jpg) image/jpeg +
- AIFF (.aif, .aiff) audio/aiff +
- WAV (.wav) audio/x-wav or audio/wav +
+
+ |
+
Deep Blue Preservation and Format Support Policy
+ +Deep Blue (hereafter the "Repository") is committed to +providing long-term access to all deposited content by applying best practices +for data management and digital preservation while also acknowledging the +complexities involved in preserving digital information. The Repository commits +to preserving the content in the form it is originally deposited and, for some +formats, will preserve the content, structure and functionality of the files +through migration or other preservation strategies. In addition, the Repository +will provide basic services including secure storage, backup, management, +fixity-checks, and periodic refreshment by copying the data to new storage +media.
+ +At the outset, the Repository will provide three levels of +preservation support for specific file formats. We have determined these +support levels by applying a set of evaluation criteria including prevalence of +the file format in the marketplace, whether the format is proprietary, the +availability +of tools for emulation or migration and the availability of local resources to +take specific preservation actions. The Repository will undertake appropriate +format monitoring and provide adequate staffing and other resources to support +the services offered at each level. Over time, our ability to provide full +preservation support for more formats is likely to grow as additional tools and +techniques are developed. To assist content creators in saving and depositing +documents that meet the level of quality necessary for full information capture +and the highest degree of preservability over time, Deep Blue is developing a +set of specification and format best-practice guidelines for common content +types.
+ +The Repository provides three levels of support for various submission file +formats.
+ +Level 1
+ +The Repository will provide its highest level of preservation +support, making +its best effort to maintain the content, structure and functionality in the +future. This service level is currently provided only for formats that are both +publicly documented and widely used, giving us a high degree of confidence in +our preservation commitment, making it more likely that tools will exist or be +developed to undertake preservation actions, and that those actions will result +in an understood and controlled transformation or migration. The content may +also be normalized (transformed to another stable format) to provide additional +assurance that the information content is preserved. Finally, the content will +be preserved as originally deposited to ensure the original bitstream is always +available. TIFF is an example of a Level 1-supported format, as its +specifications are publicly available, it is well-supported and widely +deployed.
+ ++ +
Level 2
+ +The Repository will make limited efforts to maintain the +usability +of the file as well as preserving it as submitted (bit-level preservation). The +format will be monitored and may be transformed when significant risk to access +is imminent but it is likely to be difficult to predict or control the +consequences of any transformation or migration on content, structure or +functionality. The file may also be transformed to a more preservable format to +ensure that the information content is not lost, even if some structure and +functionality are sacrificed. This level of support is generally applied to +proprietary formats that are widely used, where there is substantial commercial +interest in maintaining access to files saved in the format, and therefore +tools will likely be available to migrate them to successor formats (e.g., +Microsoft Word).
+ ++ +
Level 3
+ +The Repository provides basic preservation of the file +(bitstream) and associated metadata as-is with no active effort +made to monitor the format and +associated risks or to normalize, transform or migrate the file to another +format. Files may be openable and/or readable by future applications, but there +is no guarantee that the content, structure, or functionality will be +preserved. This service level usually applies to files written in highly +specialized, proprietary formats, often usable only in a single software +environment, formats no longer widely utilized, and/or formats about which +little information is publicly available. PhotoCD is an example of a format +that would receive Level 3 support in the Repository. Any format not yet +reviewed and evaluated by Deep Blue will also receive Level 3 service on +deposit. A higher level may be assigned after format review takes place.
+ ++ +
The following chart summarizes the primary preservation +services that Deep Blue will provide at the various service levels:
+ ++ +
| Feature |
+ Level 1 |
+ Level 2 |
+ Level 3 |
+
| Persistent identifier that will always point to the object and/or its metadata |
+ • |
+ • |
+ • |
+
| Provenance records and other preservation metadata to support accessibility and management over time |
+ • |
+ • |
+ • |
+
| Secure storage and backup |
+ • |
+ • |
+ • |
+
| Periodic refreshment to new storage media |
+ • |
+ • |
+ • |
+
| Fixity checks using proven checksum methods |
+ • |
+ • |
+ • |
+
| Storage in a trusted preservable format (making a normalized version, if necessary) |
+ • |
+ for some formats |
+ + |
| Strategic monitoring of format |
+ • |
+ • |
+ + |
| Migration to succeeding format upon obsolescence |
+ • |
+ + | + |
The three levels of preservation commitment are made at the +individual file level. Complex content items comprised of multiple files in +various formats will need additional evaluation to determine whether the +operational relationships between the files can be maintained. If the original +relationships are documented externally in metadata, that information will be +preserved in any case. In addition, executables and some files that rely on a +specific hardware/software environment will require additional evaluation +because not only the format but the access environment must be considered in +making a preservation determination. Because of the collection policy for +accepting finished work, we discourage submissions in some "working" formats, +such as Photoshop and Final Cut Pro, since we will be unable to offer the +highest level of preservation support for them. If you have material to deposit +that fall into any of these categories, please contact the Deep Blue +Preservation Group prior to making your deposit.
+ ++ +
Registered Formats and Support Levels
+ +This list of formats and support levels will be regularly reviewed and + update based on our growing experience with digital preservation and the +emergence of new formats and standards.
+ ++ +
Last updated March 9, 2011
+ ++ +
|
+ TEXT AND PAGE DESCRIPTION FORMATS (Best Practices For Creating Quality PDFs) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ PDF/A + |
+
+ |
+
+ application/pdf + |
+
+ Level 1 + |
+
+ Best Practices
+ |
+
|
+ Plain Text UTF-8 (Unicode) + |
+
+ .txt + |
+
+ text/plain; charset=UTF-8 + |
+
+ Level 1 + |
+
+ + |
+
|
+ Plain Text ANSI X3.4/ECMA-6/US-ASCII (7-bit) + |
+
+ .txt + |
+
+ text/plain; charset=US-ASCII + |
+
+ Level 1 + |
+
+ + |
+
|
+ SGML + |
+
+ .sgm, .sgml + |
+
+ application/sgml + |
+
+ Level 1 + |
+
+ Requires that DTD is deposited with SGML file and that SGML file parses against it + |
+
|
+ XML + |
+
+ .xml + |
+
+ text/xml + |
+
+ Level 1 /
+ |
+
+ Level 1 requires that DTD/schema is deposited with XML file and that XML file parses against it; Level 2 assumes no DTD/schema but that XML file is well-formed + |
+
|
+ HTML + |
+
+ .html, .htm + |
+
+ text/html + |
+
+ Level 2 + |
+
+ Requires HTML 4.0 or 4.01 validated markup and CSS files(s), if referenced, be deposited with document + |
+
|
+ LaTeX + |
+
+ .latex + |
+
+ application/x-latex + |
+
+ Level 2 /
+ |
+
+ Level 2 requires that referenced style files and/or embedded items be deposited with document + |
+
|
+ Postscript + |
+
+ .ps + |
+
+ application/ps + |
+
+ Level 2 + |
+
+ + |
+
|
+ Rich Text + |
+
+ .rtf + |
+
+ text/richtext + |
+
+ Level 2 + |
+
+ + |
+
|
+ TeX + |
+
+ .tex + |
+
+ application/x-tex + |
+
+ Level 2 /
+ |
+
+ Level 2 requires that referenced style files and/or embedded items be deposited with document + |
+
|
+ Plain Text ISO 8859-x
+ |
+
+ .txt + |
+
+ text/plain; charset=ISO-8859-x + |
+
+ Level 2 + |
+
+ + |
+
|
+ Plain Text; |
+
+ .txt + |
+
+ text/plain + |
+
+ Level 3 + |
+
+ + |
+
+ +
|
+ COMMON DESKTOP SOFTWARE FORMATS (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ Microsoft Word + |
+
+ .doc + |
+
+ application/msword + |
+
+ Level 2 + |
+
+ Requires that macros be disabled + |
+
|
+ Microsoft PowerPoint + |
+
+ .ppt + |
+
+ application/ |
+
+ Level 2 + |
+
+ Requires that macros, animation and other effects be disabled + |
+
|
+ Microsoft Excel + |
+
+ .xls + |
+
+ application/vnd.ms-excel + |
+
+ Level 2 + |
+
+ Requires that macros be disabled. (See also Best Practices for Datasets) + |
+
+ +
|
+ IMAGE FILE FORMATS (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ JPEG + |
+
+ .jpg + |
+
+ image/jpeg + |
+
+ Level 1 + |
+
+ + |
+
|
+ TIFF + |
+
+ .tiff + |
+
+ image/tiff + |
+
+ Level 1 + |
+
+ + |
+
|
+ JPEG 2000 + |
+
+ + |
+
+ + |
+
+ Level 2 + |
+
+ Level 1 support expected as more tools become available + |
+
|
+ PNG + |
+
+ .png + |
+
+ image/png + |
+
+ Level 2 + |
+
+ + |
+
|
+ BMP + |
+
+ .bmp + |
+
+ image/x-ms-bmp + |
+
+ Level 3 + |
+
+ + |
+
|
+ GIF + |
+
+ .gif + |
+
+ image/gif + |
+
+ Level 3 + |
+
+ + |
+
|
+ Photo CD + |
+
+ .pcd + |
+
+ image/x-photo-cd + |
+
+ Level 3 + |
+
+ + |
+
|
+ Photoshop + |
+
+ .psd + |
+
+ application/x-photoshop + |
+
+ Level 3 + |
+
+ + |
+
+ +
|
+ AUDIO (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ AIFF + |
+
+ .aif, .aiff + |
+
+ audio/aiff, + + |
+
+ Level 1 + |
+
+ + |
+
|
+ Wave + |
+
+ .wav + |
+
+ audio/x-wav or audio/wav + |
+
+ Level 1 + |
+
+ + |
+
|
+ Audio/Basic + |
+
+ .au, .snd + |
+
+ audio/basic + |
+
+ Level 2 + |
+
+ + |
+
|
+ MPEG audio + |
+
+ .mp3 + |
+
+ audio/mpeg, audio/mp3 + |
+
+ Level 2 + |
+
+ + |
+
|
+ AAC_M4A + |
+
+ m4a, .mp4 + |
+
+ audio/m4a, audio/mp4 + |
+
+ Level 2 + |
+
+ + |
+
|
+ Real Audio + |
+
+ .ra, .rm, .ram + |
+
+ audio/vnd.rn-realaudio + |
+
+ Level 3 + |
+
+ + |
+
|
+ Windows Media Audio + |
+
+ .wma + |
+
+ audio/x-ms-wma + |
+
+ Level 3 + |
+
+ + |
+
+ +
|
+ VIDEO (Best Practices) + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ AVI + |
+
+ .avi + |
+
+ video/avi, video/msvideo, video/x-msvideo + + |
+
+ Level 2 + |
+
+ + |
+
|
+ Quicktime + |
+
+ .mov + |
+
+ video/quicktime, video/x-quicktime + |
+
+ Level 2 + |
+
+ + |
+
|
+ MPEG-1 |
+
+ .mp1 |
+
+ video/mpeg |
+
+ Level 2 + |
+
+ Many variants possible; preservation level not yet established + |
+
|
+ MPEG-4 + |
+
+ .mp4 + |
+
+ video/mp4 + |
+
+ Level 2 + |
+
+ Many variants possible; preservation level not yet established + |
+
|
+ Windows Media Video + |
+
+ .wmv + |
+
+ video/x-ms-wmv + |
+
+ Level 3 + |
+
+ + |
+
+ + +
|
+ OTHER/MISCELLANEOUS + |
+ ||||
|
+ Format + |
+
+ File Extension + |
+
+ Mime Type + |
+
+ Support Level + |
+
+ Qualifying Factors/Notes + |
+
|
+ ZIP/tar + |
+
+ .zip, .gz, tar.gz + |
+
+ application/zip; application/x-gzip + |
+
+ Level 1; see "Qualifying Factors/Notes" + |
+
+ ZIP or tar files are only as good as their contents; all best practices above still apply. (See also Best practices for producing ZIP and tar files) + |
+
+
+ |
+
Your Privacy in Deep Blue
+ + ++Your privacy is important to us, and its protection is supported by +national and state laws, specifically the Michigan Library Privacy Act as well as by UM policies and +guidelines and University Library policies.
++ +
+What information gets collected and stored automatically?
+ ++We gather information about use of Deep Blue so we can better meet your +needs and troubleshoot problems. This information, in the form of +session logs (which contain data such as browser type and IP address) is +retained for approximately 2 weeks, then discarded.
++ +
+Does Deep Blue store personally-identifiable information?
+ ++No. While we do collect some information that can identify you as an +individual user, we do not store it any longer than necessary for +troubleshooting. Additionally, the Library purges use data on items +viewed or downloaded from Deep Blue. Note, however, that information you +choose to save in the following areas is retained:
+ +-
+
- Information you store in My Deep Blue; +
- Information matching your name with the +items you deposit, and; +
- Questions and comments submitted to feedback +and help, identifiable if you provide a reply email address. +
+Access to the above information is restricted to Library staff who need +to use it in the normal course of Library business. This information is +never used for commercial or marketing purposes and will never be +revealed to any third party except by such process, order, or subpoena +authorized by national, state, or local law.
++ +
+How do you protect this information?
++To guard against unauthorized access, maintain the integrity of the +data, and promote the proper use of that data we have implemented +physical, electronic, and managerial procedures to safeguard and secure +the information we collect.
++While we consider these reasonable measures, no guarantee can be made +that they will always prevent invalid access or improper activity. For +this reason, wherever possible we delete data (such as information about +what items you have previously viewed) that might cause activities to be +linked to you as an individual.
+ + + \ No newline at end of file diff --git a/src/assets/static/about/deepblueroles.html b/src/assets/static/about/deepblueroles.html new file mode 100644 index 00000000000..0603a193f73 --- /dev/null +++ b/src/assets/static/about/deepblueroles.html @@ -0,0 +1,172 @@ + + + + + +
+
+ |
+
Roles and Responsibilities of Deep Blue Partners
+ +Deep Blue (the Repository) is a partnership between University of Michigan + (UM) communities, the University Library and University administration. Deep + Blue content consists of works and Collections produced by members of UM communities, + which are managed, preserved and distributed by the University Library through + Deep Blue. Some of the Collections may be subject to institutional guidelines + defined by the University of Michigan Standard +Practice Guide, particularly section 601.08 regarding electronic records.
+ + + +As in all partnerships, it is important that all Deep Blue stakeholders understand and agree to the policies, guidelines and procedures required to build the repository. The following policy statement outlines the roles, rights and responsibilities of the partners as developed by the Deep Blue steering committee. It will be reviewed and revised regularly.
++ +
Deep Blue Community Definition
+ +A Deep Blue "Community" is an academic or administrative unit at UM that produces creative, intellectual, or artistic work, has a defined leader, has long-term stability, and can assume responsibility for setting Collection policies. Each Community must be able to assign Collection Administrators/Coordinators who can work with Deep Blue staff. A partial list of research entities can be found at www.umich.edu/res_activ.htm, +which may serve as a guide for establishing communities.
+ +Groups wishing to establish a Deep Blue Collection that do not fall into this + definition will be considered on a case-by-case basis. The University Library + will also assist individuals in locating or establishing Communities and Collections to host +their work.
++ +
Deep Blue Community Responsibilities
+ +A Deep Blue Community agrees to:
+ +-
+
- understand and observe University policies relevant to Deep Blue, and educate + Collection depositors regarding these policies +
- clear copyright for items deposited when copyright owner is other than author(s) + or UM +
- make decisions about Community and Collection definitions +
- notify Deep Blue of organizational changes affecting submissions +
- reply to periodic reconfirmation of Community information +
- arrange for deposit and description of content +
- establish a deposit workflow for each collection +
+
Deep Blue Community Rights
+ +A Deep Blue Community retains the right to:
+ +-
+
- decide policy regarding + content to be deposited (within Deep Blue guidelines, as outlined in the +FAQ, e.g. "What types of content +can be deposited in Deep Blue?") +
- limit access to content at the item level either to UM only or to specific individuals + or groups for a Community-defined period of time +
- decide who may deposit content within the Community's Collections +
- remove items and Collections + (as outlined in "Withdrawal of Items" below) +
- receive + a copy of deposited content upon request +
- control the organization and presentation of Collection contents +
- customize interfaces to Collection contents using existing Deep Blue functionality +
+
University Library Responsibilities
+ +The Repository agrees to:
+ +-
+
- retain and maintain content deposited to Deep Blue +
- maintain the system that supports persistent URLs/URIs +
- distribute content according to Community decisions (access must be extended to UM + authorized users, unless prior approval is granted by Deep Blue Policy + Committee) +
- preserve content using accepted preservation techniques per our Preservation Policy +
- provideaccess to Deep Blue content +
- notify Communities of significant preservation actions, e.g. format migration +
- if a Community ceases to exist, offer their Collections for transfer to the University Archives (the Bentley Historical Library) within Deep Blue +
- if content deposited in Deep Blue is deemed to be + official University records, it may transfer the control of that content to + University Archives, housed at the Bentley Historical Library, while + remaining in Deep Blue. +
See Deep Blue Services for +additional information about support available to Deep Blue users.
+ ++
University Library Rights
+The Repository retains the right to:
+ +-
+
- amend + and/or redistribute descriptive information (metadata) for items in Deep + Blue +
- refuse or withdraw items or + Collections under certain circumstances - as outlined in the FAQ, + e.g. "What types of content can be deposited in Deep Blue?") +
- renegotiate terms of deposit agreements with Communities +
- perform appraisal for transfer or other disposition when Communities cease to exist +
- institute pre-deposit selection or appraisal if financial constraints require that limits be placed on the RepositoryÕs operations +
- move Collections to reflect changing agreements between Deep Blue and Communities +
- migrate items if format is in danger of obsolescence +
- set quotas for size of files, number of items +
+ +
University Responsibilities
+UM is expected to set policy at +the University level regarding issues that affect Deep Blue, e.g. copyright +rules, thesis requirements, etc.
+ ++ +
Withdrawal of items from Deep Blue
+The Library foresees times when it +may be necessary to remove items from the repository and has decided that under +some circumstances items will be removed from view. To avoid loss of the +historical record, all such transactions will be traced and visible via a +provenance statement. The content of the note should be one of the following: +
-
+
- "Removed from view by legal order." +
- "Removed from view by the University of Michigan." +
- "Removed from view at request of the author." +
The tombstone metadata will be visible to those who already have its persistent + URL, but your deposit and its metadata will no longer be searchable and we + will make these items unavailable for harvesting by services such as OAIster + and Google.
+ +Since any Deep Blue item that has +been available may have been cited, we will supply a 'tombstone' record. When +the item is requested, the original metadata (for verification) plus one of the +above withdrawal statements will be displayed in place of the link to the +object. The metadata for withdrawn items will be visible, but not searchable +or available for metadata harvesting.
+ + + + \ No newline at end of file diff --git a/src/assets/static/about/deepblueservices.html b/src/assets/static/about/deepblueservices.html new file mode 100644 index 00000000000..bf5d113731a --- /dev/null +++ b/src/assets/static/about/deepblueservices.html @@ -0,0 +1,239 @@ + + + + + +
+
+ |
+
Deep Blue Services
+ +As outlined below, the University +of Michigan (UM) Library offers deposit, access, and preservation services to +support Deep Blue and its users. Additionally, the Library provides community +management, end-user support, and system management services to provide ongoing +support for Deep Blue communities, respond to user inquiries, and supply system +monitoring, back-up, and recovery. We are investigating services beyond those +in the Deep Blue Basic Service which may be offered through a "Premium Service" +model.
+ ++
Deposit Services
+ +Deep Blue offers contributors a flexible, easy-to-use +deposit process. A contributor completes a brief deposit form and grants +non-exclusive permission to distribute and preserve the work.
+ +-
+
- Register with Deep Blue and edit his/her user profile +
- Add a deposit to a specified collection +
- Enter descriptive information (metadata) for a deposit +
- Include additional metadata with a deposit +
- Bundle multiple files of various formats in a single deposit +
- Identify formats of deposited files +
- Grant a non-exclusive license to UM to distribute a deposit in accordance with + the specified distribution policy and translate it for the purposes of + preservation +
- Receive updates on the progress of an item through the deposit workflow process +
- View past and pending deposits in a personalized "My Deep Blue" page. +
Communities may decide to subject +new deposits to a review and approval process, customized to a community's +needs. The community administrator(s) establish workflows of the deposit +process and create the reviewer, coordinator and metadata editor roles during + a community's or collection's initial set-up. This process may include the +following roles and steps:
+ +-
+
- Reviewer: can review all content submitted to a collection and decide to accept or + reject a deposit +
- Coordinator: can edit metadata for all deposit and decide to accept or reject a deposit +
- Editor: can only edit the metadata for a deposit +
Through the deposit workflow process, reviewers, coordinators, +and metadata editors can:
+ +-
+
- Augment and approve deposits and deposit metadata in the workflow process +
- Review the content of a deposit for appropriateness to the collection and make + the decision to route a deposit back to the person who submitted it or to + give approval +
- Check the deposit's metadata for completeness and obvious errors, edit errors, + and make the decision to route a deposit back to the depositor or give + approval +
- View, select, and perform workflow tasks from the "Pending Workflow Tasks" + section of his/her personalized "My Deep Blue" page +
+
Access Services
+Deep Blue's Access Services give +users the ability to browse, search, and discover items of interest, request +one or more items from the system, and take delivery of the requested items. +Those interested in accessing the contents of Deep Blue can:
+ +-
+
- Browse Deep Blue contents by title, author, or community/collection +
- Search for items anywhere in Deep Blue, or within a particular community or + collection. +
- Search for matches within author, title, or full text words and view results +
- View an item overview, including: Deep Blue core metadata, list of collections + that contain this item, and links to each of the files (text, image, etc.) + that comprise the item +
- View the contents of an item online +
- Download an individual item and view it within a web browser or save the file to a + specified location. +
+
Repository Services and Quotas
+ +Deep Blue provides storage and +preservation services to ensure the longevity of deposited materials. Users +should be assured that content deposited in many formats (see Preservation +Policy) will be accessible even when the original +application in which it was created is obsolete and the means to access it are +inoperable. For each deposit, Deep Blue:
+ +-
+
- Provides persistent storage, including appropriate back-up and recovery procedures +
- Assigns a unique persistent identifier (URI) that will not change and is + appropriate to cite in other works +
- Supports a range of service levels for preservation and notifies users of Deep + Blue's preservation constraints +
- Stores provenance information. +
- Maintains an auditable history and record of changes to Deep Blue +
Initial storage quotas will be +based on the size of the Deep Blue community as determined by the Library. +Thereafter, the quotas will be reviewed on an annual basis at which time the +Library reserve the right to alter the quotas as dictated by demand and +resource availability. Communities with greater storage needs can contact Deep +Blue's administrators for further assistance.
+ ++
Community Management Services
+Deep Blue's Community Management +Services are a set of consultative and applied services designed to meet the +needs of individual communities. Library staff will provide guidance in +developing a community or collection's workflow process, metadata requirements, +and distribution policies as well as launching a Deep Blue community homepage.
+ + +The Library will manage all +aspects of the community set-up process, including:
+ +-
+
- Planning + and scheduling new community and collection set-ups +
- At the request of a community, facilitating an initial community discussion + and explaining set-up requirements +
- Assisting in training community users and coordinators +
- Implementing custom workflow for the deposit process including metadata defaults +
- Assisting in customizing Deep Blue community and collection home pages +
- Assisting with ongoing collection set-ups +
- Specifying a collection's distribution policy and license requirements +
- Coordinating bulk loads of historic content and metadata. +
A local coordinator—typically +a Library liaison or subject specialist—will help provide Community +Management Services with back-up from the Deep Blue Coordinator and the Systems +Administrator.
++
End-User Support Services
+ +The Library will provide both +web-based and telephone support to all Deep Blue users. Support will be provided Monday through Friday, 9:00am to 5:00pm. Inquiries +will typically receive a return response via e-mail or telephone within one +business day.
+ + +The Deep Blue web site will provide documentation, +including FAQs to +answer routine questions and user support contact information for more complex +questions.
+ + +Library liaisons and subject +specialists will work with the Deep Blue coordinator and Systems Administrator +to provide End-User Support Services, with back-up from the Digital Library +Production Services and its Core Services staff.
++
System Management Services
+ + +System Management Services are the +back-office support for Deep Blue, working to ensure optimal system performance +and high availability.
+ + +The UM Library will provide a +comprehensive set of technical services for Deep Blue system operations, +including:
+ + +-
+
- Performing system monitoring, testing and debugging +
- Performing system administration +
- Monitoring and upgrading Deep Blue utility programs and middleware +
- Developing approved system enhancements +
- Performing bulk loading of historic content and metadata +
- Maintaining a registry of known content and metadata formats for preservation + purposes. +
The Deep Blue Systems Administrator will provide System +Management Services with back-up from the Digital Library Production Services +and its Core Services staff. The UM Library will provide 24/7 support for Deep +Blue's server, storage and network operations.
+ + + +Premium Services
+ + +The Library is investigating the +introduction of a set of Premium Services to meet the exceptional resource +requirements of Deep Blue communities. Deep Blue was designed as a distributed +system that allows communities to manage their own collections, and the areas listed +above include all necessary functionality to achieve that. As with any new +service, though, it is difficult to determine how users will employ specific +features of the system and the resulting services they will demand. The Library +anticipates that some Deep Blue communities may want to outsource certain +activities to the Library or may put demands on the system that require +additional resources for support.
+ + + + \ No newline at end of file diff --git a/src/assets/static/about/favicon.ico b/src/assets/static/about/favicon.ico new file mode 100644 index 00000000000..94b8fd4fe86 Binary files /dev/null and b/src/assets/static/about/favicon.ico differ diff --git a/src/assets/static/about/image/MLibraryLogo.gif b/src/assets/static/about/image/MLibraryLogo.gif new file mode 100644 index 00000000000..985cf6d8fa9 Binary files /dev/null and b/src/assets/static/about/image/MLibraryLogo.gif differ diff --git a/src/assets/static/about/image/MLibraryLogo2.gif b/src/assets/static/about/image/MLibraryLogo2.gif new file mode 100644 index 00000000000..763c9b22e40 Binary files /dev/null and b/src/assets/static/about/image/MLibraryLogo2.gif differ diff --git a/src/assets/static/about/image/arrow-highlight.gif b/src/assets/static/about/image/arrow-highlight.gif new file mode 100644 index 00000000000..18ce29b8ecc Binary files /dev/null and b/src/assets/static/about/image/arrow-highlight.gif differ diff --git a/src/assets/static/about/image/arrow.gif b/src/assets/static/about/image/arrow.gif new file mode 100644 index 00000000000..e64d6654f59 Binary files /dev/null and b/src/assets/static/about/image/arrow.gif differ diff --git a/src/assets/static/about/image/authority/book_key.png b/src/assets/static/about/image/authority/book_key.png new file mode 100644 index 00000000000..d8e23ec9329 Binary files /dev/null and b/src/assets/static/about/image/authority/book_key.png differ diff --git a/src/assets/static/about/image/authority/bug.png b/src/assets/static/about/image/authority/bug.png new file mode 100644 index 00000000000..2d5fb90ec6e Binary files /dev/null and b/src/assets/static/about/image/authority/bug.png differ diff --git a/src/assets/static/about/image/authority/load-indicator.gif b/src/assets/static/about/image/authority/load-indicator.gif new file mode 100644 index 00000000000..a22a8d0c1a0 Binary files /dev/null and b/src/assets/static/about/image/authority/load-indicator.gif differ diff --git a/src/assets/static/about/image/authority/readme.txt b/src/assets/static/about/image/authority/readme.txt new file mode 100644 index 00000000000..fbd9cec5454 --- /dev/null +++ b/src/assets/static/about/image/authority/readme.txt @@ -0,0 +1,35 @@ +==== + The contents of this file are subject to the license and copyright + detailed in the LICENSE and NOTICE files at the root of the source + tree and available online at + + http://www.dspace.org/license/ +==== +The following icon files: +- book_key.png +- zoom.png +- bug.png +are taken from + +Silk icon set 1.3 + +_________________________________________ +Mark James +http://www.famfamfam.com/lab/icons/silk/ +_________________________________________ + +This work is licensed under a +Creative Commons Attribution 2.5 License. +[ http://creativecommons.org/licenses/by/2.5/ ] + +This means you may use it for any purpose, +and make any changes you like. +All I ask is that you include a link back +to this page in your credits. + +Are you using this icon set? Send me an email +(including a link or picture if available) to +mjames@gmail.com + +Any other questions about this icon set please +contact mjames@gmail.com \ No newline at end of file diff --git a/src/assets/static/about/image/authority/zoom.png b/src/assets/static/about/image/authority/zoom.png new file mode 100644 index 00000000000..908612e3945 Binary files /dev/null and b/src/assets/static/about/image/authority/zoom.png differ diff --git a/src/assets/static/about/image/banner-large.jpg b/src/assets/static/about/image/banner-large.jpg new file mode 100644 index 00000000000..983b50dec13 Binary files /dev/null and b/src/assets/static/about/image/banner-large.jpg differ diff --git a/src/assets/static/about/image/banner-small.jpg b/src/assets/static/about/image/banner-small.jpg new file mode 100644 index 00000000000..eeb64e15fc4 Binary files /dev/null and b/src/assets/static/about/image/banner-small.jpg differ diff --git a/src/assets/static/about/image/bluestream_deepblue1.jpg b/src/assets/static/about/image/bluestream_deepblue1.jpg new file mode 100644 index 00000000000..800426fb006 Binary files /dev/null and b/src/assets/static/about/image/bluestream_deepblue1.jpg differ diff --git a/src/assets/static/about/image/bluestream_deepblue7.jpg b/src/assets/static/about/image/bluestream_deepblue7.jpg new file mode 100644 index 00000000000..1eb03301693 Binary files /dev/null and b/src/assets/static/about/image/bluestream_deepblue7.jpg differ diff --git a/src/assets/static/about/image/cc-somerights.gif b/src/assets/static/about/image/cc-somerights.gif new file mode 100644 index 00000000000..0c01840514d Binary files /dev/null and b/src/assets/static/about/image/cc-somerights.gif differ diff --git a/src/assets/static/about/image/cc-somerights2.gif b/src/assets/static/about/image/cc-somerights2.gif new file mode 100644 index 00000000000..a66f4d1a010 Binary files /dev/null and b/src/assets/static/about/image/cc-somerights2.gif differ diff --git a/src/assets/static/about/image/confidence/0-unauthored.gif b/src/assets/static/about/image/confidence/0-unauthored.gif new file mode 100644 index 00000000000..05f7b48c870 Binary files /dev/null and b/src/assets/static/about/image/confidence/0-unauthored.gif differ diff --git a/src/assets/static/about/image/confidence/2-errortriangle.gif b/src/assets/static/about/image/confidence/2-errortriangle.gif new file mode 100644 index 00000000000..77ecac66969 Binary files /dev/null and b/src/assets/static/about/image/confidence/2-errortriangle.gif differ diff --git a/src/assets/static/about/image/confidence/2-lightning.gif b/src/assets/static/about/image/confidence/2-lightning.gif new file mode 100644 index 00000000000..5f458266867 Binary files /dev/null and b/src/assets/static/about/image/confidence/2-lightning.gif differ diff --git a/src/assets/static/about/image/confidence/2-warntriangle.gif b/src/assets/static/about/image/confidence/2-warntriangle.gif new file mode 100644 index 00000000000..03f658fd18e Binary files /dev/null and b/src/assets/static/about/image/confidence/2-warntriangle.gif differ diff --git a/src/assets/static/about/image/confidence/3-circleslash.gif b/src/assets/static/about/image/confidence/3-circleslash.gif new file mode 100644 index 00000000000..c834095ba81 Binary files /dev/null and b/src/assets/static/about/image/confidence/3-circleslash.gif differ diff --git a/src/assets/static/about/image/confidence/3-flag.gif b/src/assets/static/about/image/confidence/3-flag.gif new file mode 100644 index 00000000000..35857f99400 Binary files /dev/null and b/src/assets/static/about/image/confidence/3-flag.gif differ diff --git a/src/assets/static/about/image/confidence/3-thumb1.gif b/src/assets/static/about/image/confidence/3-thumb1.gif new file mode 100644 index 00000000000..8fec573875f Binary files /dev/null and b/src/assets/static/about/image/confidence/3-thumb1.gif differ diff --git a/src/assets/static/about/image/confidence/3-thumb2.gif b/src/assets/static/about/image/confidence/3-thumb2.gif new file mode 100644 index 00000000000..ee6aea8f218 Binary files /dev/null and b/src/assets/static/about/image/confidence/3-thumb2.gif differ diff --git a/src/assets/static/about/image/confidence/4-question.gif b/src/assets/static/about/image/confidence/4-question.gif new file mode 100644 index 00000000000..7b20d616f67 Binary files /dev/null and b/src/assets/static/about/image/confidence/4-question.gif differ diff --git a/src/assets/static/about/image/confidence/4-star.gif b/src/assets/static/about/image/confidence/4-star.gif new file mode 100644 index 00000000000..da6654c3fcc Binary files /dev/null and b/src/assets/static/about/image/confidence/4-star.gif differ diff --git a/src/assets/static/about/image/confidence/5-pinion.gif b/src/assets/static/about/image/confidence/5-pinion.gif new file mode 100644 index 00000000000..e48a5e035e4 Binary files /dev/null and b/src/assets/static/about/image/confidence/5-pinion.gif differ diff --git a/src/assets/static/about/image/confidence/5-star.gif b/src/assets/static/about/image/confidence/5-star.gif new file mode 100644 index 00000000000..55e8b079a35 Binary files /dev/null and b/src/assets/static/about/image/confidence/5-star.gif differ diff --git a/src/assets/static/about/image/confidence/6-greencheck.gif b/src/assets/static/about/image/confidence/6-greencheck.gif new file mode 100644 index 00000000000..91f949b40ce Binary files /dev/null and b/src/assets/static/about/image/confidence/6-greencheck.gif differ diff --git a/src/assets/static/about/image/confidence/6-star.gif b/src/assets/static/about/image/confidence/6-star.gif new file mode 100644 index 00000000000..de8f2fa587c Binary files /dev/null and b/src/assets/static/about/image/confidence/6-star.gif differ diff --git a/src/assets/static/about/image/confidence/6-thumb1.gif b/src/assets/static/about/image/confidence/6-thumb1.gif new file mode 100644 index 00000000000..3233f650bd6 Binary files /dev/null and b/src/assets/static/about/image/confidence/6-thumb1.gif differ diff --git a/src/assets/static/about/image/confidence/6-thumb2.gif b/src/assets/static/about/image/confidence/6-thumb2.gif new file mode 100644 index 00000000000..7fdc37091ac Binary files /dev/null and b/src/assets/static/about/image/confidence/6-thumb2.gif differ diff --git a/src/assets/static/about/image/confidence/invisible.gif b/src/assets/static/about/image/confidence/invisible.gif new file mode 100644 index 00000000000..17d43908d5e Binary files /dev/null and b/src/assets/static/about/image/confidence/invisible.gif differ diff --git a/src/assets/static/about/image/confidence/readme.txt b/src/assets/static/about/image/confidence/readme.txt new file mode 100644 index 00000000000..c91e09d0bea --- /dev/null +++ b/src/assets/static/about/image/confidence/readme.txt @@ -0,0 +1,53 @@ +==== + The contents of this file are subject to the license and copyright + detailed in the LICENSE and NOTICE files at the root of the source + tree and available online at + + http://www.dspace.org/license/ +==== +16x16 Free Application Icons + +This icon set is free for use in personal and commercial projects. + +License Agreement + +By purchasing icons from Aha-Soft, You (the purchaser) +agree to the terms of this agreement, as detailed below. + +You may use the icons from Aha-Soft in commercial and +personal design projects, software or Internet products. +Icons can be displayed in documentation, help files, and +advertising materials. You are free to sell and distribute +products and projects using purchased icons without further +royalty fees. + +All icon files are provided 'as is'. Aha-Soft cannot be +held liable for any negative issues that may occur as a +result of using the icons. + +You agree that all ownership and copyright of the icons +remains the property of Aha-Soft. You may not resell, +distribute, lease, license or sub-license the icons or +modified icons (or a subset of the icons), to any third +party unless they are incorporated into your software or +design products. + +If you have any questions regarding copyright or licensing, +including whether another license is required for icon use +within products, please contact us here: www.aha-soft.com/support.htm + +Product page: http://www.small-icons.com/stock-icons/16x16-free-application-icons.htm + +Icon Design Service + +We can design custom icons for you. Please find the basic information +about ordering icons, pricing and the portfolio here: +www.aha-soft.com/customdev/design.htm + + +Notice +Web-site small-icons.com belongs to Aha-Soft. + +Support page: http://www.aha-soft.com/support.htm + +Copyright � 2009 Aha-Soft. All rights reserved. \ No newline at end of file diff --git a/src/assets/static/about/image/controlledvocabulary/f.gif b/src/assets/static/about/image/controlledvocabulary/f.gif new file mode 100644 index 00000000000..550a47f8ee2 Binary files /dev/null and b/src/assets/static/about/image/controlledvocabulary/f.gif differ diff --git a/src/assets/static/about/image/controlledvocabulary/m.gif b/src/assets/static/about/image/controlledvocabulary/m.gif new file mode 100644 index 00000000000..81054a1e2b8 Binary files /dev/null and b/src/assets/static/about/image/controlledvocabulary/m.gif differ diff --git a/src/assets/static/about/image/controlledvocabulary/p.gif b/src/assets/static/about/image/controlledvocabulary/p.gif new file mode 100644 index 00000000000..980edc6c253 Binary files /dev/null and b/src/assets/static/about/image/controlledvocabulary/p.gif differ diff --git a/src/assets/static/about/image/deepbluepmc.jpg b/src/assets/static/about/image/deepbluepmc.jpg new file mode 100644 index 00000000000..8dcc95d15e3 Binary files /dev/null and b/src/assets/static/about/image/deepbluepmc.jpg differ diff --git a/src/assets/static/about/image/deepbluetype1.gif b/src/assets/static/about/image/deepbluetype1.gif new file mode 100644 index 00000000000..ae58907723a Binary files /dev/null and b/src/assets/static/about/image/deepbluetype1.gif differ diff --git a/src/assets/static/about/image/dome-bluewhite-smaller.gif b/src/assets/static/about/image/dome-bluewhite-smaller.gif new file mode 100644 index 00000000000..513dc3d40f6 Binary files /dev/null and b/src/assets/static/about/image/dome-bluewhite-smaller.gif differ diff --git a/src/assets/static/about/image/drop1.gif b/src/assets/static/about/image/drop1.gif new file mode 100644 index 00000000000..4ff0504a129 Binary files /dev/null and b/src/assets/static/about/image/drop1.gif differ diff --git a/src/assets/static/about/image/drop1home.gif b/src/assets/static/about/image/drop1home.gif new file mode 100644 index 00000000000..de385152b8e Binary files /dev/null and b/src/assets/static/about/image/drop1home.gif differ diff --git a/src/assets/static/about/image/dspace-blue.gif b/src/assets/static/about/image/dspace-blue.gif new file mode 100644 index 00000000000..644d23176db Binary files /dev/null and b/src/assets/static/about/image/dspace-blue.gif differ diff --git a/src/assets/static/about/image/flying-man.jpg b/src/assets/static/about/image/flying-man.jpg new file mode 100644 index 00000000000..22d0262c080 Binary files /dev/null and b/src/assets/static/about/image/flying-man.jpg differ diff --git a/src/assets/static/about/image/hp-mit.gif b/src/assets/static/about/image/hp-mit.gif new file mode 100644 index 00000000000..1d27f80fe59 Binary files /dev/null and b/src/assets/static/about/image/hp-mit.gif differ diff --git a/src/assets/static/about/image/hp.gif b/src/assets/static/about/image/hp.gif new file mode 100644 index 00000000000..edcabdfbfee Binary files /dev/null and b/src/assets/static/about/image/hp.gif differ diff --git a/src/assets/static/about/image/lock.gif b/src/assets/static/about/image/lock.gif new file mode 100644 index 00000000000..83a129da501 Binary files /dev/null and b/src/assets/static/about/image/lock.gif differ diff --git a/src/assets/static/about/image/lock24.png b/src/assets/static/about/image/lock24.png new file mode 100644 index 00000000000..89ebada2f32 Binary files /dev/null and b/src/assets/static/about/image/lock24.png differ diff --git a/src/assets/static/about/image/navbarBG.gif b/src/assets/static/about/image/navbarBG.gif new file mode 100644 index 00000000000..388a91dc423 Binary files /dev/null and b/src/assets/static/about/image/navbarBG.gif differ diff --git a/src/assets/static/about/image/remove.gif b/src/assets/static/about/image/remove.gif new file mode 100644 index 00000000000..f9533698ade Binary files /dev/null and b/src/assets/static/about/image/remove.gif differ diff --git a/src/assets/static/about/image/rss.gif b/src/assets/static/about/image/rss.gif new file mode 100644 index 00000000000..70e6fc62491 Binary files /dev/null and b/src/assets/static/about/image/rss.gif differ diff --git a/src/assets/static/about/image/rss1.gif b/src/assets/static/about/image/rss1.gif new file mode 100644 index 00000000000..430842e5a16 Binary files /dev/null and b/src/assets/static/about/image/rss1.gif differ diff --git a/src/assets/static/about/image/rss2.gif b/src/assets/static/about/image/rss2.gif new file mode 100644 index 00000000000..f21da7e84a3 Binary files /dev/null and b/src/assets/static/about/image/rss2.gif differ diff --git a/src/assets/static/about/image/search-go.gif b/src/assets/static/about/image/search-go.gif new file mode 100644 index 00000000000..ac5f4639189 Binary files /dev/null and b/src/assets/static/about/image/search-go.gif differ diff --git a/src/assets/static/about/image/searchbtbl.gif b/src/assets/static/about/image/searchbtbl.gif new file mode 100644 index 00000000000..ec19c67961e Binary files /dev/null and b/src/assets/static/about/image/searchbtbl.gif differ diff --git a/src/assets/static/about/image/searchlines1.gif b/src/assets/static/about/image/searchlines1.gif new file mode 100644 index 00000000000..6361cf97d51 Binary files /dev/null and b/src/assets/static/about/image/searchlines1.gif differ diff --git a/src/assets/static/about/image/sfx-link.gif b/src/assets/static/about/image/sfx-link.gif new file mode 100644 index 00000000000..7747ccb817a Binary files /dev/null and b/src/assets/static/about/image/sfx-link.gif differ diff --git a/src/assets/static/about/image/spacer.gif b/src/assets/static/about/image/spacer.gif new file mode 100644 index 00000000000..79a04abc5b0 Binary files /dev/null and b/src/assets/static/about/image/spacer.gif differ diff --git a/src/assets/static/about/image/star-background.jpg b/src/assets/static/about/image/star-background.jpg new file mode 100644 index 00000000000..690cc963f34 Binary files /dev/null and b/src/assets/static/about/image/star-background.jpg differ diff --git a/src/assets/static/about/image/stripe.gif b/src/assets/static/about/image/stripe.gif new file mode 100644 index 00000000000..b06b894b70e Binary files /dev/null and b/src/assets/static/about/image/stripe.gif differ diff --git a/src/assets/static/about/image/submit/Complete-current.gif b/src/assets/static/about/image/submit/Complete-current.gif new file mode 100644 index 00000000000..a46789cede8 Binary files /dev/null and b/src/assets/static/about/image/submit/Complete-current.gif differ diff --git a/src/assets/static/about/image/submit/Complete-done.gif b/src/assets/static/about/image/submit/Complete-done.gif new file mode 100644 index 00000000000..c7c2c6430dc Binary files /dev/null and b/src/assets/static/about/image/submit/Complete-done.gif differ diff --git a/src/assets/static/about/image/submit/Complete-notdone.gif b/src/assets/static/about/image/submit/Complete-notdone.gif new file mode 100644 index 00000000000..27f8a1c8105 Binary files /dev/null and b/src/assets/static/about/image/submit/Complete-notdone.gif differ diff --git a/src/assets/static/about/image/submit/Describe-current.gif b/src/assets/static/about/image/submit/Describe-current.gif new file mode 100644 index 00000000000..f6dd2a4cdcc Binary files /dev/null and b/src/assets/static/about/image/submit/Describe-current.gif differ diff --git a/src/assets/static/about/image/submit/Describe-done.gif b/src/assets/static/about/image/submit/Describe-done.gif new file mode 100644 index 00000000000..5c2f2284b39 Binary files /dev/null and b/src/assets/static/about/image/submit/Describe-done.gif differ diff --git a/src/assets/static/about/image/submit/Describe-notdone.gif b/src/assets/static/about/image/submit/Describe-notdone.gif new file mode 100644 index 00000000000..f39cea6dcd4 Binary files /dev/null and b/src/assets/static/about/image/submit/Describe-notdone.gif differ diff --git a/src/assets/static/about/image/submit/License-current.gif b/src/assets/static/about/image/submit/License-current.gif new file mode 100644 index 00000000000..c139760b0f6 Binary files /dev/null and b/src/assets/static/about/image/submit/License-current.gif differ diff --git a/src/assets/static/about/image/submit/License-done.gif b/src/assets/static/about/image/submit/License-done.gif new file mode 100644 index 00000000000..ede6a84c4b1 Binary files /dev/null and b/src/assets/static/about/image/submit/License-done.gif differ diff --git a/src/assets/static/about/image/submit/License-notdone.gif b/src/assets/static/about/image/submit/License-notdone.gif new file mode 100644 index 00000000000..14dddd855b0 Binary files /dev/null and b/src/assets/static/about/image/submit/License-notdone.gif differ diff --git a/src/assets/static/about/image/submit/Upload-current.gif b/src/assets/static/about/image/submit/Upload-current.gif new file mode 100644 index 00000000000..70302a866c3 Binary files /dev/null and b/src/assets/static/about/image/submit/Upload-current.gif differ diff --git a/src/assets/static/about/image/submit/Upload-done.gif b/src/assets/static/about/image/submit/Upload-done.gif new file mode 100644 index 00000000000..ebeec3959b2 Binary files /dev/null and b/src/assets/static/about/image/submit/Upload-done.gif differ diff --git a/src/assets/static/about/image/submit/Upload-notdone.gif b/src/assets/static/about/image/submit/Upload-notdone.gif new file mode 100644 index 00000000000..da4bd78d996 Binary files /dev/null and b/src/assets/static/about/image/submit/Upload-notdone.gif differ diff --git a/src/assets/static/about/image/submit/Verify-current.gif b/src/assets/static/about/image/submit/Verify-current.gif new file mode 100644 index 00000000000..227846b78ae Binary files /dev/null and b/src/assets/static/about/image/submit/Verify-current.gif differ diff --git a/src/assets/static/about/image/submit/Verify-done.gif b/src/assets/static/about/image/submit/Verify-done.gif new file mode 100644 index 00000000000..34dd9a8c5e1 Binary files /dev/null and b/src/assets/static/about/image/submit/Verify-done.gif differ diff --git a/src/assets/static/about/image/submit/Verify-notdone.gif b/src/assets/static/about/image/submit/Verify-notdone.gif new file mode 100644 index 00000000000..ea7f2fbf5ec Binary files /dev/null and b/src/assets/static/about/image/submit/Verify-notdone.gif differ diff --git a/src/assets/static/about/image/submit/current.gif b/src/assets/static/about/image/submit/current.gif new file mode 100644 index 00000000000..5646a8299d3 Binary files /dev/null and b/src/assets/static/about/image/submit/current.gif differ diff --git a/src/assets/static/about/image/submit/done.gif b/src/assets/static/about/image/submit/done.gif new file mode 100644 index 00000000000..130fc6b8338 Binary files /dev/null and b/src/assets/static/about/image/submit/done.gif differ diff --git a/src/assets/static/about/image/submit/notdone.gif b/src/assets/static/about/image/submit/notdone.gif new file mode 100644 index 00000000000..611bc3e9221 Binary files /dev/null and b/src/assets/static/about/image/submit/notdone.gif differ diff --git a/src/assets/static/about/image/swoosh.gif b/src/assets/static/about/image/swoosh.gif new file mode 100644 index 00000000000..e36744be5af Binary files /dev/null and b/src/assets/static/about/image/swoosh.gif differ diff --git a/src/assets/static/about/image/unlock24.png b/src/assets/static/about/image/unlock24.png new file mode 100644 index 00000000000..fae950dcd32 Binary files /dev/null and b/src/assets/static/about/image/unlock24.png differ diff --git a/src/assets/static/about/image/valid-xhtml10.png b/src/assets/static/about/image/valid-xhtml10.png new file mode 100644 index 00000000000..b81de9160bb Binary files /dev/null and b/src/assets/static/about/image/valid-xhtml10.png differ diff --git a/src/assets/static/about/index.html b/src/assets/static/about/index.html new file mode 100644 index 00000000000..866d5979b14 --- /dev/null +++ b/src/assets/static/about/index.html @@ -0,0 +1,165 @@ + + + + + + + + +
+
+ |
+
+
|
+
+
+
+ Deep Blue provides access to the work that makes the University of Michigan a leader in research, teaching, and creativity. By representing our faculty, staff, and student scholars as individuals and as members of communities, Deep Blue is where you will find and the Library preserves the best scholarly and artistic work done at Michigan. + + +What you get when you use Deep Blue: + +
The University Library provides this service free to you as part of the UM scholarly community. Further, Deep Blue is designed to meet not only today's demands but also new ones as they evolve. It will continue to grow and evolve to reflect current publishing needs and norms identified by UM faculty, staff, students, and the communities you form. + + +Your work: cited more, safe forever. Deep Blue makes it simple. + + |
+
+|||||||||||||||||
|
+ |
+||||||||||||||||||
+