Web and DAMS - NC ECHO Dig Institute

1,390 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,390
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Web and DAMS - NC ECHO Dig Institute

  1. 1. Putting Your Digital Collections on the Web Emily Gore, NC ECHO Project Manager [email_address]
  2. 2. What We’re Going to Cover <ul><li>Defining websites, web design, content management systems and digital asset management systems </li></ul><ul><li>Website basics – HTML and beyond </li></ul><ul><li>Planning a web presence for your digital project/program </li></ul><ul><li>Digital Asset Management Systems – what are they, what do they cost, why are they important? </li></ul><ul><li>Web 2.0 and beyond – thinking differently about the web we know </li></ul>
  3. 3. What’s a Website? <ul><li>A collection of web pages, images, videos and other digital assets hosted on a particular domain on the World Wide Web. </li></ul><ul><li>As of March 2007, there are over 110 million websites on the WWW. </li></ul><ul><li>Website is hosted on a computer system known as a web server or an HTTP server. </li></ul><ul><li>These servers run software that retrieves and delivers web pages in response to requests by users. Apache and IIS are the 2 most common web server software packages. </li></ul>
  4. 4. URL Anatomy <ul><li>URL = uniform resource locator AKA web address </li></ul><ul><li>http:// https:// ftp:// = protocol </li></ul><ul><li>DNS (domain name server) = www.ncecho.org </li></ul>
  5. 5. Website Basics <ul><li>Language of the web is largely HTML (hypertext markup language) </li></ul><ul><li>- HTML is a defined set of tags i.e. <b>, <p>, <li></li> </li></ul><ul><li>- HTML is a subset of SGML (standard generalized markup language) </li></ul><ul><li>- SGML is the parent and HTML the child </li></ul>
  6. 6. Standard HTML Tags <ul><li><html></html> </li></ul><ul><li><head></head> </li></ul><ul><li><body></body> </li></ul><ul><li><bgcolor> </li></ul><ul><li><font></font> </li></ul><ul><li><table></table> <tr> <td> </li></ul><ul><li><center> <align> </li></ul><ul><li><li> </li></ul>
  7. 7. Example of a Standard Static HTML Page <ul><li>State Library of North Carolina </li></ul><ul><li>View the source in your browser window </li></ul><ul><li>Do you see some of the tags referred to on the previous slide? </li></ul>
  8. 8. Dynamic Web Design <ul><li>HTML is often referred to as “static” </li></ul><ul><li>Many websites are “dynamic” or database-driven </li></ul><ul><li>There are 2 ways of delivering content dynamically – server-side or client-side scripting often called “includes” </li></ul>
  9. 9. Server-side <ul><li>a web server, running special software, constructs an HTML page on the fly according to a user’s request </li></ul><ul><li>Examples of scripting languages include: </li></ul><ul><li>ASP </li></ul><ul><li>ASP.NET </li></ul><ul><li>PHP </li></ul><ul><li>JSP </li></ul><ul><li>Cold Fusion (CFM) </li></ul><ul><li>Ruby </li></ul>
  10. 10. Client-side <ul><li>Client-side scripting works in the user’s browser. </li></ul><ul><li>It is more suited for decoration or ephermeral content because of browser dependence </li></ul><ul><li>Most often achieved through Javascript </li></ul><ul><li>Client-side DHTML can pose major problems for web accessibility and are normally not recommended unless alternative navigation is provided </li></ul>
  11. 11. Style <ul><li>Websites often have CSS (Cascading Style Sheets) to define their look, feel and position </li></ul><ul><li>CSS is a simple mechanism for defining fonts, colors, spacing, etc. for your website </li></ul><ul><li>CSS is often used to control and standardize a website for a consistent look and feel </li></ul>
  12. 12. CSS Example <ul><li>p {font-family: “Garamond”, serif; } </li></ul><ul><li>h2 {font-size: 110%; color: red; background: white;} </li></ul><ul><li>This is a simple CSS that defines the paragraph and h2 (level 2) heading elements. </li></ul><ul><li>The paragraph will be rendered in Garamond font if available. If not, it will be rendered in another serif font. </li></ul><ul><li>The level 2 heading will be rendered at 110% in red on a white background. </li></ul>
  13. 13. Transforming a website w/ CSS <ul><li>Example: </li></ul><ul><li>http://www.csszengarden.com </li></ul><ul><li>With the widespread use of CSS, the need use of <table> for layout purposes is much less </li></ul>
  14. 14. Hosting options <ul><li>Purchase, install and maintain your own web server </li></ul><ul><li>Pay a hosting service to host your website on their web server </li></ul><ul><ul><li>Many services from $5/month+ depending on size of the website and the amount of website traffic </li></ul></ul>
  15. 15. Purchasing Your Domain <ul><li>Use a domain name locator service </li></ul><ul><li>Give it a try: </li></ul><ul><ul><li>http://www.register.com </li></ul></ul><ul><ul><li>Does someone own the address you are interested in purchasing? Look up the WHOIS data to find out who owns the address you are interested in. </li></ul></ul>
  16. 16. Already Own a Domain? <ul><li>If your library or museum already has a web presence, you could possibly start building your digital collections as part of that domain </li></ul><ul><li>You may also want to create a subdomain on that server for your collections </li></ul><ul><ul><li>Subdomain example: http://digital.lib.ecu.edu/ </li></ul></ul><ul><ul><li>Original Domain: http://www.lib.ecu.edu/ </li></ul></ul><ul><ul><li>Subdomain vs. Folder: digital.lib.ecu.edu VS www.lib.ecu.edu/digital </li></ul></ul><ul><ul><li>A subdomain allows for unique identity </li></ul></ul>
  17. 17. Planning a Web Presence for Your Digital Project <ul><li>Web pages with metadata vs. Digital Asset Management Systems </li></ul><ul><li>How web pages and DAMS work together ( UNC DeBry ) </li></ul><ul><li>Your web presence is the way the world sees all the work you have put into your digital project </li></ul><ul><li>What do you want to convey? </li></ul><ul><li>Who is your audience? </li></ul>
  18. 18. Digital Asset Management Systems or Repositories <ul><li>Digital asset management systems are computer software and hardware systems that aid in ingesting, annotating, describing, storing and retrieving digital assets, such as digital photographs, videos, music, or text. </li></ul>
  19. 19. “Off the Shelf”, Open Source Custom or Build Your Own <ul><li>Pros and Cons for Each </li></ul><ul><li>Consider: </li></ul><ul><ul><li>Time </li></ul></ul><ul><ul><li>Staff </li></ul></ul><ul><ul><li>Expertise </li></ul></ul><ul><ul><li>Technical Infrastructure (or lack) </li></ul></ul><ul><ul><li>Needs of your organization and user population </li></ul></ul>
  20. 20. “Off the Shelf” <ul><li>“ Off the Shelf” Example*: </li></ul><ul><ul><li>ContentDM (OCLC) </li></ul></ul><ul><ul><li>DigiTool (Ex Libris) - FSU Digital Collections </li></ul></ul><ul><ul><li>Luna Insight (David Rumsey) - David Rumsey Map Collection </li></ul></ul><ul><ul><li>DLXS (Michigan) - Michigan Museum of Modern Art </li></ul></ul><ul><li>Content webpages link to digital objects housed in the DAMS </li></ul><ul><li>Takes expertise to customize and may still not meet your needs, as it is not designed for just your needs </li></ul><ul><li>Customer support and maintanence </li></ul><ul><li>Pricing starting at as little as $1,000 to more than $50,000 </li></ul><ul><li>*NC ECHO in NO way endorses these products. These are common products used in digital libraries throughout the country that are being used here as examples only. </li></ul>
  21. 21. Open Source DAMS <ul><li>Open Source Custom Examples: </li></ul><ul><ul><li>Fedora (Cornell) - Tufts </li></ul></ul><ul><ul><li>DSpace (MIT) - UMD </li></ul></ul><ul><ul><li>Greenstone - Auburn </li></ul></ul><ul><ul><li>MDID (JMU) - JMU </li></ul></ul><ul><li>Free (at least for the software) </li></ul><ul><li>Community support instead of technical support </li></ul><ul><li>Much development and customization is often necessary </li></ul><ul><li>Often requires a large amount of time, resources and expertise to implement </li></ul><ul><li>Often results in a customized, institution-specific solution if time, resources and expertise are available </li></ul>
  22. 22. Build Your Own <ul><li>Two Examples in NC: </li></ul><ul><li>DocSouth – SQL/PHP custom-built solution </li></ul><ul><li>East Carolina’s ENCore – ASP.NET/C# custom-built solution </li></ul>
  23. 23. Likely Options for digital project/program websites <ul><li>1)Content webpages with thumbnails and larger access images/VR and appropriate metadata </li></ul><ul><li>2)Content webpages linking to a digital asset management system, where digital object and metadata are housed </li></ul>
  24. 24. Examples From Option #1 <ul><li>History of Forestry Project @ NCSU </li></ul><ul><li>Photograph Collection from the Heritage Room, Monroe, NC (Union Cty PL) </li></ul><ul><li>Meredith College Dolls </li></ul>
  25. 25. Examples from Option #2 <ul><li>Horace Kephart: Revealing an Enigma (WCU) </li></ul><ul><li>Tobacco Bag Stringing (UNC) </li></ul><ul><li>Green ’N’ Growing (NCSU) </li></ul>
  26. 26. Principles of Good Design <ul><li>No matter how you choose to go about building your web presence, good design principles are essential </li></ul><ul><li>Consider your main audience and then the general public (if it is on the web, it’s open to the world) </li></ul><ul><li>What do you want your site to convey? </li></ul>
  27. 27. Principles of Good Design <ul><li>Not only LOOKS good, but WORKS good </li></ul><ul><li>Consistent Navigation – don’t make it confusing for your users </li></ul><ul><li>Easy to Find Contact Information </li></ul><ul><li>Metadata About Digital Objects and Collections (on-screen and embedded) </li></ul><ul><li>Browser Independence </li></ul><ul><li>Clarity </li></ul><ul><li>Legible Fonts </li></ul>
  28. 28. Accessibility <ul><li>Section 508 defines guidelines for website accessibility for persons with disabilities </li></ul><ul><li>Graphics and multimedia must have descriptive text labels </li></ul><ul><li>Information conveyed by color must be available when color is missing </li></ul><ul><li>Frames must have titles – Try to avoid when possible </li></ul><ul><li>Provide alternatives to client-side javascripting or applet functions that can be used by assistive technologies </li></ul>
  29. 29. Bobby <ul><li>Think of a URL you want to test for accessibility or use one of the sites we have looked at today </li></ul><ul><li>Type that URL in to Bobby to check compliance: </li></ul><ul><ul><li>http://webxact.watchfire.com </li></ul></ul><ul><li>How would you fix the problems if any are found? </li></ul>
  30. 30. Web 2.0 – Food For Thought <ul><li>Perceived as second-generation of web-based communities and hosted services – such as social networking sites (i.e. blogs ), wikis and folksonomies/ tag clouds – that facilitate collaboration and sharing between users.* </li></ul><ul><li>Changing user expectations – are we meeting those expectations? </li></ul><ul><li>How will this change the way we build digital projects/programs? </li></ul><ul><li>*Wikipedia.com </li></ul>
  31. 31. Questions?

×