Merge pull request #101 from sul-dlss/more-branding-updates

More branding updates

README.md

@@ -135,7 +135,7 @@ Bump VERSION file by editing it in master
 
     bundle exec cap prod deploy     # for production  
     bundle exec cap stage deploy    # for staging     
-    bundle exec cap dev deploy      # for development 
+    bundle exec cap dev deploy      # for development
 
 You must specify a branch to deploy.  You can deploy the latest by specifying "master".  You should never be deploying anything except master to prod.
 
@@ -154,13 +154,13 @@ Digital Library.  For example, if you wanted to add a new field, you need to:
 
 1. Be sure the MODs template gets updated to the new field is stored appropriately during accessioning.  The MODs templates are in /config/templates.
 2. Ensure the new field has a column in the metadata spreadsheet supplied. The name of the column in the spreadsheet should match what is in the MODs template you edited in step 1.
-3. Update the Revs template in editstore-updater to be sure metadata edits coming from the site make it to the MODs correctly.  In the editstore-updater code  (https://github.com/sul-dlss/editstore-updater), this is in the app/models/template/revs.rb file in the "field_definitions" method.  Configure with the name of the solr field and the location in the MODs template.  After deploying editstore-updater, be sure to visit the UI (https://revslib.stanford.edu/editstore/projects/2) and confirm you see the fields in the list.
+3. Update the Revs template in editstore-updater to be sure metadata edits coming from the site make it to the MODs correctly.  In the editstore-updater code  (https://github.com/sul-dlss/editstore-updater), this is in the app/models/template/revs.rb file in the "field_definitions" method.  Configure with the name of the solr field and the location in the MODs template.  After deploying editstore-updater, be sure to visit the UI (https://automobility.stanford.edu/editstore/projects/2) and confirm you see the fields in the list.
 4. Update the revs-indexing-service code (https://github.com/sul-dlss/revs-indexer-service) to be sure the MODs is correctly indexed into solr.  You'll need to update the lib/revs_mapper.rb class (in the convert_to_solr_doc method).
 5. Update the revs-utils gem, which has shared configuration around available fields.
  -- add the new fields in the lib/revs-utils.rb file in the "revs_field_mapping" method.  Configuration specifies the accessor name along with the solr field name.
  -- update config/manifest_headers.yml to add the new columns that will appear in spreadsheets
  -- bump and release the gem
-6. Update the revs digital library website code (this codebase) to show the new field and make it editable (if necessary), and add it as a facet (if necessary).
+6. Update the website code (this codebase) to show the new field and make it editable (if necessary), and add it as a facet (if necessary).
  -- add facets in the catalog controller if necessary
  -- update the "bulk_update_fields" method in ApplicationHelper if this new field is available for bulk updating by curators
  -- update the app/views/catalog/_show_default_collection_member.html.erb view to add the new field to the appropriate part of the interface

VERSION

@@ -1 +1 @@
-December-2017
+December-2017a

app/assets/stylesheets/_print.scss

@@ -55,6 +55,6 @@
     padding-top: 12px;
   }
   #content p a:after {
-    content: " (http://revslib.stanford.edu/" attr(href) ")";
+    content: " (https://automobility.stanford.edu/" attr(href) ")";
   }
 }

app/mailers/revs_mailer.rb

@@ -2,7 +2,7 @@ class RevsMailer < ActionMailer::Base
 
   helper :application
   include ApplicationHelper
-  default from: "no-reply@revslib.stanford.edu"
+  default from: "no-reply@automobility.stanford.edu"
 
   def contact_message(opts={})
     params=opts[:params]
@@ -23,20 +23,20 @@ def new_users_notification(opts={})
     to=Revs::Application.config.new_registration_notification
     mail(:to=>to,:subject=>I18n.t('revs.contact.notification_new_users')) if valid_email?(to)
   end
-  
+
   def auto_response(opts={})
     @email=opts[:email]
     @subject=opts[:subject]
     mail(:to=>@email,:subject=>I18n.t('revs.contact.thanks')) if valid_email?(@email)
   end
-  
+
   def flag_resolved(flag)
     @flag=flag
     mail(:to=>flag.user.email,:subject=>I18n.t('revs.flags.resolved_message')) if flag.user && flag.user.email && valid_email?(flag.user.email)
   end
-  
+
   def mailing_list_signup(opts={})
     mail(:to=>"revs-program-join@lists.stanford.edu",:from=>opts[:from],:subject=>"Request to be added to the Revs Program Mailing List",:body=>"Subscribe")
   end
-  
+
 end

app/views/curator/help/bulk_edits.html.erb

@@ -8,7 +8,7 @@
   <h3>Edit multiple records in bulk (bulk editing)</h3>
 
   <p>
-    The Revs Digital Library includes a feature that enables a curator to
+    The Automobility Archive includes a feature that enables a curator to
     update a single metadata field with a given value for multiple records at one
     time. This can be a very efficient way to add new values, or update existing
     values, for a group of related item records. For example, a group of
@@ -19,7 +19,7 @@
   </p>
 
   <p>
-    When you are logged into Revs as a curator and conduct a search, you'll see
+    When you are logged into the archive as a curator and conduct a search, you'll see
     an additional view available on the search results page, called
     <code>Curator</code> The screenshot below shows the Curator view for a search
     on <code>Thompson Raceway</code> narrowed by <code>Year > 1966</code>:
@@ -96,7 +96,7 @@
   <h4>Ideas for bulk edits</h4>
   <p>
     The bulk edit feature can be used to update sets of records with the same, incorrect
-    value, but it can also be used to improve the Revs Digital Library by quickly
+    value, but it can also be used to improve the Archive by quickly
     adding values to fields that have currently contain no values, enriching the
     metadata record for those items and making the Revs search and browse features
     more effective for end-users. Here are some ideas that knowledgable curators

app/views/revs_mailer/auto_response.html.erb

@@ -1,3 +1,2 @@
-Thanks for contacting the Revs Digital Library!  If you are requesting access to or want to download an image from The Revs Institute Archives, you should receive
-a message directly from The Revs Institute in Naples, Florida.  For other issues, we may not be able to respond individually.
-You can also review our <a href="http://revslib.stanford.edu/about/faq">Frequently Asked Questions (FAQ)</a> for more information.
+Thanks for contacting the Automobility Archive!  If you are requesting access to or want to download an image, please review the reuse requirements.  Note that we may not be able to respond individually.
+You can also review our <a href="https://automobility.stanford.edu/about/faq">Frequently Asked Questions (FAQ)</a> for more information.

app/views/revs_mailer/contact_message.html.erb

@@ -4,7 +4,7 @@
     <meta charset="utf-8" />
   </head>
   <body>
-<p>Contact Us message from Revs Digital Library:</p>
+<p>Contact Us message from Automobility Archive:</p>
 <p>Time submitted: <%=Time.now%></p>
 <p>Subject: <%=@subject%></p>
 <p>Name: <%=@fullname%></p>
@@ -15,4 +15,4 @@
 <p>Message: <%=@message%></p>
 <p>Source Page: <%=@from%></p>
 <p>User agent: <%=@request.env["HTTP_USER_AGENT"]%></p>
-</body></html>
+</body></html>

app/views/revs_mailer/flag_resolved.html.erb

@@ -1,5 +1,5 @@
 <p>
-You previously flagged a correction to an item in the Revs Digital Library 
+You previously flagged a correction to an item in the Automobility Archive
 <% unless @flag.comment.blank? %> with the comment '<%=@flag.comment%>' <% end %> and the flag was resolved on <%=show_as_date(@flag.resolved_time)%> by <%=@flag.resolved_by.to_s%> with the status '<%=@flag.state_display_name%>'.
 <% unless @flag.resolution.blank? %> The curator also added a comment of '<%=@flag.resolution%>'.<% end %>
 </p>

app/views/revs_mailer/new_users_notification.erb

@@ -4,5 +4,5 @@
     <meta charset="utf-8" />
   </head>
   <body>
-<p><%=@num_users%> users have registered on the Revs Digital Library and require activation.</p>
-</body></html>
+<p><%=@num_users%> users have registered on the Automobility Archive and require activation.</p>
+</body></html>

config/application.rb

@@ -119,5 +119,5 @@ class Application < Rails::Application
   end
 end
 
-GOOGLE_ANALYTICS_CODE = "UA-7219229-17" # revs digital library
+GOOGLE_ANALYTICS_CODE = "UA-7219229-17" # automobility archive
 EDITSTORE_PROJECT='Revs'  # the name of your project in the editstore database -- this must exist in the edistore database "projects" table in both production and development to work properly

config/environments/production.rb

@@ -4,7 +4,7 @@
 
   # Settings specified here will take precedence over those in config/application.rb
   config.exception_error_page = true # show a friendly 500 error page and send notification exceptions if true
-  config.action_mailer.default_url_options = { :host => 'revslib.stanford.edu' }
+  config.action_mailer.default_url_options = { :host => 'automobility.stanford.edu' }
 
   # Code is not reloaded between requests
   config.cache_classes = true

config/initializers/is_it_working.rb

@@ -12,33 +12,33 @@
   h.check :active_record, :async => false
 
   # Check the home page
-  h.check :url, :get => "https://revslib.stanford.edu"
+  h.check :url, :get => "https://automobility.stanford.edu"
 
   # Check the about page
-  h.check :url, :get => "https://revslib.stanford.edu/about"
+  h.check :url, :get => "https://automobility.stanford.edu/about"
 
   # check an item detail page
-  h.check :url, :get => "https://revslib.stanford.edu/item/yk807wq6530"
+  h.check :url, :get => "https://automobility.stanford.edu/item/tp537fn9045"
 
   h.check :search_result do |status|
-    url="https://revslib.stanford.edu/?q=chevrolet"
+    url="https://automobility.stanford.edu/?q=buick"
     response = RestClient.get(url)
     fail 'has a bad response' unless response.code == 200
-    if response.body.include?("<strong>1</strong> - <strong>10</strong> of ") # could be any number of large results
+    if response.body.include?("<strong>1</strong> - <strong>10</strong> of") # could be any number of large results
       status.ok('has results')
     else
-      status.ok('is missing results')
+      fail 'is missing results'
     end
   end
 
   h.check :collections_page do |status|
-    url="https://revslib.stanford.edu/collection"
+    url="https://automobility.stanford.edu/collection"
     response = RestClient.get(url)
     fail 'has a bad response' unless response.code == 200
-    if response.body.include?("<strong>1</strong> - <strong>12</strong> of ") # could be any number greater than 12
+    if response.body.include?("Road & Track magazine records") # the road & track archive
       status.ok('has results')
     else
-      status.ok('is missing results')
+      fail 'is missing results'
     end
   end
 

config/locales/about.en.yml

@@ -20,7 +20,7 @@ en:
       terms_continue: 'Continue'
       terms_disagree: 'Do not continue'
       acknowledgements_text_html: |
-        
+
       copyright_infringement: 'report alleged copyright infringement to Stanford'
       terms_of_use_policy: 'Stanford University Terms of Use Policy'
       contributors_title: 'Top Contributors'
@@ -98,4 +98,4 @@ en:
           <h3>Road & Track Archive</h3>
           <p>The Road & Track Archive contains a digitized selection of files from Road & Track magazine's 65-year history.  The full archive includes images, notes, performance data and other types of documents and research that supported production of the magazine over its history.</p>
           <p>Among the gems from the full archives: original photography from the '50s and '60s, a sampling of the collection's 2,000 books and even old letters from manufacturers complaining to Road & Track editors about negative product reviews.</p>
-          <p>The archive once filled a two-car garage at Road & Track's Newport Beach facility before the magazine moved to Michigan, and now resides in Stanford Libraries' Special Collections, where they are available on request for academic research.  As additional materials are digited, they will become available in the Revs Digital Library.</p>
+          <p>The archive once filled a two-car garage at Road & Track's Newport Beach facility before the magazine moved to Michigan, and now resides in Stanford Libraries' Special Collections, where they are available on request for academic research.  As additional materials are digited, they will become available in the Automobility Archive.</p>

config/sitemap.rb

@@ -1,5 +1,5 @@
 # Set the host name for URL creation
-SitemapGenerator::Sitemap.default_host = "http://revslib.stanford.edu"
+SitemapGenerator::Sitemap.default_host = "https://automobility.stanford.edu"
 
 SitemapGenerator::Sitemap.create do
 

public/robots.txt

@@ -19,4 +19,4 @@ User-Agent: *
 Disallow: /catalog/range_limit
 Disallow: /catalog/facet
 
-Sitemap: http://revslib.stanford.edu/sitemap.xml.gz
+Sitemap: https://automobility.stanford.edu/sitemap.xml.gz