Projects http://rickgaribay.net/category/28.aspx Projects en-US Rick G. Garibay rickgaribay@hotmail.com Subtext Version 1.9.5.176 On Sprint Duration http://rickgaribay.net/archive/2013/09/10/on-sprint-duration.aspx <p><font size="2">I recently had a good internal discussion on 2 week versus 3 week sprints getting ready to kick off a new project for a client.</font></p> <p><font size="2">This is a debate that's been happening in the agile community for well over a decade, and while there is now broad consensus 10 years later that 4 weeks is almost always highly undesirable, the thing to remember is that the quality, caliber and discipline of the team is absolutely essential regardless of sprint duration.</font></p> <p> <br /><strong><font size="2">I Just Want to Dance!</font></strong></p> <p><font size="2">The most common argument against two week sprints is that the planning ceremonies occupy too much time and effectively reduce the team's delivery time from 10 days to less than 8. This is true for severely under-performing teams. High performing teams should be able to land demo and retro in one day and planning in as little as half a day. If the only time a team communicates is during these ceremonies, the time will drag on even further. </font></p> <p><font size="2">Performing teams communicate and practice dress rehearsals of demos, have a backlog groomed and ready to go and in some cases, might even have stories already decomposed and ready to go (signaling strong alignment with business prioritization).  <br /></font></p> <p><strong><font size="2">Deployment Happens</font></strong></p> <p><font size="2">The other common argument is that deployment time cuts further into delivery time, and now that 8 days is more like 7 days because it takes a day to deploy. This is true of teams that are practitioners of </font><a href="http://en.wikipedia.org/wiki/Cargo_cult_science"><font size="2">cargo cult agile development</font></a><font size="2">. If you don't have unit tests and automated builds in place, you _will_ feel pain each and every sprint. <br /></font></p> <p><strong><font size="2">Snake Oil</font></strong></p> <p><font size="2">One solution to this dilemma that sometimes comes up is to start with say 3 week sprints and then, when the team has "earned" 2 week sprints, reduce the sprint time accordingly. This is an anti-pattern for the simple reason that you can't improve what you can't measure and if you go around changing sprint duration, velocity becomes corrupt. This means that your ability to predict future velocity is severely impeded which affects budget, staffing and obviously has schedule implications. <br /></font></p> <p><strong><font size="2">Why Two Week Sprints Work</font></strong></p> <p><font size="2">Two week sprints are highly advantageous when you have a high degree of risk and delivering new innovation because they provide tighter intervals with which to adapt and adjust. While 3 week sprints can be successful, most often they are merely masking the lack of efficiency of the team and providing a fig leaf to hide behind- in my experience in almost every case, you will find that productive, heads down time turns out to still be just under 2 weeks!</font></p> <p><font size="2">When building a team, you should settle for no less than A-Team players that are going to kick ass and take names from day one. If you do the heavily lifting to invest in building the right team, the sprint duration won't matter nearly as much, but if you are not committed to this from day zero, no amount of sprint duration optimization will save you from failure.</font></p> <p><font size="2"></font></p><img src="http://rickgaribay.net/aggbug/358.aspx" width="1" height="1" /> Rick G. Garibay http://rickgaribay.net/archive/2013/09/10/on-sprint-duration.aspx Wed, 11 Sep 2013 00:21:18 GMT http://rickgaribay.net/archive/2013/09/10/on-sprint-duration.aspx#feedback http://rickgaribay.net/comments/commentRss/358.aspx http://rickgaribay.net/services/trackbacks/358.aspx Windows Server AppFabric Cookbook is Out! http://rickgaribay.net/archive/2012/07/26/windows-server-appfabric-cookbook-is-out.aspx <p>I'm very pleased to announce the release of my new book "Windows Server AppFabric Cookbook" which hit distribution today, July 26, 2012. <a href="http://www.packtpub.com/microsoft-windows-server-appfabric-cookbook/book"><img style="margin: 5px; display: inline; float: right" alt="Microsoft Windows Server AppFabric Cookbook" align="right" src="http://www.packtpub.com/sites/default/files/4187EN_Microsoft%20Windows%20Server%20AppFabric%20Cookbook.jpg" width="357" height="454" /></a></p> <p>Before I get into the details of the book, I want to start by thanking my co-author and friend <a href="http://twitter.com/HammadRajjoub">Hammad Rajjoub</a> for inviting me to participate in this project and trusting me to help carry out his vision for this book. Hammad and I both share a labor of love as it applies to the Microsoft distributed technology stack affectionately (and somewhat nostalgically) known as "Connected Systems" and this project represents nearly a year of work in bringing our collective experience to bear in this book. </p> <p>I would also like to express my appreciation to Adnan Masood and Zubair Ahmed who volunteered their time despite extremely busy schedules reviewing the book as it progressed and providing very valuable technical feedback along the way. Their time and dedication has contributed immensely to the quality of the book and any errors or things we've overlooked are our fault alone. </p> <p>Last but not least, I'd like to thank Ron Jacobs at Microsoft for writing the foreword to the book and providing his support and encouragement along the way.</p> <p><strong><font size="3">Why this book and why now?</font></strong></p> <p>It's hard to believe that Dublin has been in the wild for just over 2 years. The first release of <a href="http://www.microsoft.com/en-us/server-cloud/windows-server/appfabric.aspx">Windows Server AppFabric</a> went to GA in June, 2010 at TechEd in New Orleans (I remember how much fun I had demoing the features at the Microsoft booth during my shifts that seemed to fly by) and signaled an exciting shift in Microsoft's middleware strategy that continues today. Late last year, Microsoft added new caching features and made some branding changes to "<a href="http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx">AppFabric 1.1 for Windows Server</a>" to align with the the next wave of on-premise capabilities which further extend and build upon the Windows Server platform. Just last week, two new capabilities have shipped in beta which compliment AppFabric on premise: <a href="http://www.microsoft.com/en-us/download/details.aspx?id=30376">Service Bus 1.0 Beta for Windows Server</a> and <a href="http://www.microsoft.com/en-us/download/details.aspx?id=30369">Workflow 1.0 Beta for Windows Server</a>.</p> <p>Hammad and I are fortunate to have both worked very closely with Microsoft during the development of "Dublin", participating in software design reviews and early incubation initiatives. Since its release just over two years ago, we've advised customers of all shapes and sizes and fielded these capabilities in countless projects across various verticals. And herein lies the mission of this book: </p> <blockquote> <p><em><strong>To provide practical, real-world guidance for making the most of the capabilities offered by Windows Server AppFabric and AppFabric 1.1 for Windows Server based on our collective experiences in the field over the last two years since it's release. </strong></em></p> </blockquote> <p>The result (we hope) is not just a book, but a field manual chock-full of practical step-by-step, real-world guidance, tips and techniques that will help you build more maintainable, scalable, reliable, and secure service-oriented applications on the Windows Server Platform today. </p> <p><strong><font size="3">What is Windows Server AppFabric/AppFabric 1.1 for Windows Server?</font></strong></p> <p>Windows Server AppFabric is an extension of the Application Server Role on the Windows Server Platform. In a nutshell, Windows Server AppFabric frees Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF) Service developers from common infrastructure plumbing by providing a robust, secure, composable, and reliable platform which provides caching, hosting, and monitoring capabilities, including support for long running workflow services, all on the Windows Platform. As such, Windows Server AppFabric is an evolution of the Windows Server platform, providing essential building blocks for first-classing WCF (for code-based services) and WF (for declarative workflow services) that are built using the .NET Framework 4 and Visual Studio 2010. <br />As an extension to IIS and WAS, Windows Server AppFabric relies on IIS's proven capabilities for hosting and lifecycle management, adding additional useful capabilities for working with WCF and WF services. In addition, Windows Server AppFabric takes advantage of Windows Server's robust event tracing mechanism (also known as ETW). ETW provides optimized <br />and high-performing kernel-level instrumentation which greatly minimizes impact on the performance of WCF and WF services hosted in IIS with Windows Server AppFabric.</p> <p>Best of all, this key extension to the Windows Server Platform remains available <a href="http://www.microsoft.com/en-us/download/details.aspx?id=27115">free of charge</a>.</p> <p>Below are some helpful resources if you are interested in learning more:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/windowsserver/gg675185"><font color="#ffc000">Developer Introduction to Windows Server AppFabric (Part 1): Hosting Services</font></a> </li> <li><a href="http://msdn.microsoft.com/en-us/windowsserver/gg675186"><font color="#ffc000">Developer Introduction to Windows Server AppFabric (Part 2): Caching Services</font></a> </li> <li><a href="http://msdn.microsoft.com/en-us/library/hh351389.aspx"><font color="#ffc000">Product Documentation</font></a> </li> <li><a href="http://go.microsoft.com/fwlink/?LinkID=168906"><font color="#ffc000">Architectural Overview</font></a> </li> <li><a href="http://go.microsoft.com/fwlink/?LinkID=168903"><font color="#ffc000">Tutorials</font></a> </li> <li><a href="http://social.technet.microsoft.com/wiki/contents/articles/windows-server-appfabric-portal.aspx"><font color="#ffc000">AppFabric on the TechNet Wiki</font></a> </li> </ul> <p><strong><font size="3">Is this book for you?</font></strong></p> <p>If you are a developer who wants to avoid the same repetitive tasks when preparing your WCF and/or WF services for deployment, or an IT Pro who wants to avoid complex XML for configuring hosting and monitoring options for the services you manage, you will instantly benefit from Windows Server AppFabric.</p> <p>The book is over 400 pages long and includes over 60 recipes within 9 cohesive chapters:</p> <ul> <li><strong>Chapter 1</strong>, Installing Windows Server AppFabric, covers setting up your development environment to use Windows Server AppFabric. You'll learn how to install hosting, persistence and monitoring capabilities, including provisioning repositories, choosing the appropriate storage options, making changes to configuration after installation, and troubleshooting common (and not so common) installation issues you might encounter along the way. <br /></li> <li><strong>Chapter 2</strong>, Getting Started with AppFabric Caching, introduces Caching in Windows Server AppFabric, covering everything you need to get started with introducing this important capability to your composite applications and services. You will learn how to set up and use Caching using code and configuration options, as well as working with Caching within your applications. In addition, you'll learn how easily an existing application that relies on ASP.NET session state can immediately benefit from Windows Server AppFabric Cache, handling common error conditions, using PowerShell commandlets, and building a custom provider model. <br /></li> <li><strong>Chapter 3</strong>, Windows Server AppFabric Caching – Advanced Use Cases, builds on the concepts in the previous chapter, covering the use of Regions and Tags as well as choosing the right concurrency mode and establishing expiration, eviction, and notification policies. You will also learn advanced monitoring concepts including the use of performance counters, configuring high availability, and common troubleshooting techniques for getting the most out of Windows Server AppFabric Cache. <br /></li> <li><strong>Chapter 4</strong>, Windows Server AppFabric Hosting Fundamentals, introduces Windows Server AppFabric's hosting capabilities, covering common deployment, management, and hosting scenarios. You'll learn how to host WCF SOAP and REST services as well as simple WF services along with a number of tips and tricks for moving beyond the service template defaults. <br /></li> <li><strong>Chapter 5</strong>, More Windows Server AppFabric Hosting Features, covers additional hosting topics, including supporting long-running WF services, how your services can benefit from the Auto-Start feature, properly hosting WCF services that take advantage of Windows Azure Service Bus Relay bindings for enabling modern, hybrid scenarios as well as common PowerShell commandlets for scripting many of the tasks covered in this and the previous chapter. <br /></li> <li><strong>Chapter 6</strong>, Utilizing AppFabric Persistence, provides ample coverage of Windows Server AppFabric persistence capabilities, including configuring persistence for WF services, working with multiple persistence stores, and developing instance store, control, and query providers. This chapter also provides an in-depth walkthrough of development and configuration of custom instance, control, and query providers. <br /></li> <li><strong>Chapter 7</strong>, Monitoring Windows Server AppFabric Deployment, provides an introduction to <br />the monitoring capabilities provided by Windows Server AppFabric. Topics include collecting and viewing events from WCF and WF services, enabling tracing and configuring tracking profiles, and leveraging PowerShell cmdlets for monitoring WCF and WF services as well as the Caching service. In addition, you'll learn how to surface monitoring information to any user experience by following the sample recipe for building a custom monitoring dashboard using ASP.NET MVC and OData. <br /></li> <li><strong>Chapter 8</strong>, Scaling AppFabric Hosting, Monitoring, and Persistence, covers a common scenario for scaling Windows Server AppFabric across multiple IIS hosts. You will learn how to prepare two hosts for clustering using Microsoft NLB as well as understand deployment, management, and administration of a multi-host Windows Server AppFabric deployment that shares a common, centralized persistence store. <br /></li> <li><strong>Chapter 9</strong>, Configuring Windows Server AppFabric Security, covers what you need to know about planning and implementing a security model with Windows Server AppFabric. You will learn how to secure the caching, persistence, monitoring, and eventing (via ETW) subsystems of Windows Server AppFabric. </li> </ul> <p>If you've gotten this far, I sincerely appreciate your interest and hope you’ll consider purchasing our book ;-)</p> <p>The book is available in print and across most digital formats including Kindle, Nook, etc.:</p> <p>Packt is running some specials on the book which you can learn more about here: <a title="http://www.packtpub.com/microsoft-windows-server-appfabric-cookbook/book" href="http://www.packtpub.com/microsoft-windows-server-appfabric-cookbook/book">http://www.packtpub.com/microsoft-windows-server-appfabric-cookbook/book</a></p> <p>The book is also available on <a href="http://www.amazon.com/Microsoft-Windows-Server-AppFabric-Cookbook/dp/1849684189/ref=sr_1_sc_1?ie=UTF8&amp;qid=1343337928&amp;sr=8-1-spell&amp;keywords=windows+server+appfabic+cookbook">Amazon.com</a>, <a href="http://www.amazon.co.uk/Microsoft-Windows-Server-AppFabric-Cookbook/dp/1849684189/ref=sr_1_1?ie=UTF8&amp;qid=1343337985&amp;sr=8-1">Amazon.co.uk</a> and <a href="http://www.barnesandnoble.com/s/windows-server-appfabric-cookbook?store=allproducts&amp;keyword=windows+server+appfabric+cookbook">Barnes and Noble</a> (if the book is not immediately available, I’m told by the publisher that all shipments are en-route so any shipping delays should be minimal).</p> <p>If you purchase the book, I'd love to hear from you. Please <a href="http://rickgaribay.net/contact.aspx">drop me a line</a> or connect with me <a href="http://twitter.com/rickggaribay">@rickggaribay</a> and let me know what you think. </p> <ul></ul> <p>References:</p> <ul> <li><a href="http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&amp;id=15848">Windows Server AppFabric 1.0</a></li> <li><a href="http://www.microsoft.com/en-us/download/details.aspx?id=27115">AppFabric 1.0 for Windows Server</a></li> <li><a href="http://www.microsoft.com/en-us/download/details.aspx?id=30376">Service Bus 1.0 Beta for Windows Server</a></li> <li><a href="http://www.microsoft.com/en-us/download/details.aspx?id=30369">Workflow 1.0 Beta for Windows Server</a></li> <li><a href="http://hammadrajjoub.net/2012/03/03/have-you-booked-your-copy-of-windows-server-appfabric-cookbook-yet/">Hammad Rajjoub’s Blog</a></li> <li><a href="http://blog.adnanmasood.com/2012/01/03/microsoft-windows-server-appfabric-cookbook-available-for-pre-order/">Adnan Masood’s Blog</a></li> <li><a href="http://soa-thoughts.blogspot.com/2012/04/more-cookbooks-microsoft-windows-server.html">Steef-Jan Wiggers’ Blog</a></li> <li><a href="http://jeremiedevillard.wordpress.com/2012/04/07/windows-server-appfabric-and-biztalk-cookbook/">Jeremie Devillad’s Blog</a></li> <li><a href="http://paulsomers.blogspot.com/2012/03/windows-server-appfabric-cookbook.html">Paul Somer’s Blog</a> </li> </ul><img src="http://rickgaribay.net/aggbug/340.aspx" width="1" height="1" /> Rick G. Garibay http://rickgaribay.net/archive/2012/07/26/windows-server-appfabric-cookbook-is-out.aspx Thu, 26 Jul 2012 22:12:56 GMT http://rickgaribay.net/archive/2012/07/26/windows-server-appfabric-cookbook-is-out.aspx#feedback 3 http://rickgaribay.net/comments/commentRss/340.aspx http://rickgaribay.net/services/trackbacks/340.aspx Not So Lazy Days of Summer... http://rickgaribay.net/archive/2009/07/06/not-so-lazy-days-of-summer.aspx <p>Its been a busy year. I can't believe we are already half way through it. In a blink of an eye, here we are in July.</p> <p>I just wrapped up the manuscript for a new article for CoDe Magazine which I will talk about more once I get through the edit process (sometimes things can change after a few passes but it covers Azure Compute and Table Storage) and am heads down on a gate automation and management software product for a leading commercial transportation company. The product is a canonical software + services product with central WCF services in the cloud and lightweight clients and WCF services out in the edge. The idea is that customers who want to optimize operational expenses will install the gate management appliances at their facilities and provided they install compatible hardware, they can set up schedules and rules around when and for who the gate should open and literally set it and forget it in the cloud. The software will detect the presence of a vehicle by reading the RFID transponder, run some client-side rules and either open the gate or deny the vehicle entry to the facility.</p> <p>We are currently in our 5th Sprint (4 week sprints) and it is exciting to see the product really start to take shape. We've delivered almost all of the vertical slices as a result of the stories completed to date (each Sprint we've delivered potentially shippable software), and one of the last slices is the synchronization infrastructure for keeping the cloud and <img style="MARGIN: 10px" height="240" width="196" align="right" alt="" src="http://i.msdn.microsoft.com/bb887608.Figure1(en-us).png" />clients out in the edge in sync. To be successful, the synchronization strategy must support occasionally connected clients providing the ability to perform a one-time synchronization to bootstrap a brand new install at a facility with all the necessary data from the cloud to become operational. It also must support event-driven updates, such that the cloud publishes events of interest such as new gates, RFID devices being registered for a gate or changes to business rules and a subscribing service then initiates a JIT synchronization with the cloud. In addition, the client on the edge must be able to synchronize with the cloud (i.e. forward updates), and all of this must be a) <strong>durable</strong>, such that synchronization can resume after a network failure b) <strong>transacted</strong> such that both client(s) and cloud updates are atomic, c) <strong>interoperable</strong> such that both TCP and HTTP/S topologies can be supported and d) <strong>secure</strong>. </p> <p>To that end, I am currently implementing the next version of Microsoft Sync Framework (Sync Framework 2.0) which will be the lynchpin of our synchronization strategy first with a SQL provider followed almost immediately by a WCF SOAP provider.<a href="http://www.apress.com/book/view/9781430210054"><img style="MARGIN: 10px" height="164" alt="Pro Sync Framework book cover" width="125" align="left" border="0" src="http://www.apress.com/resource/bookcover/9781430210054?size=medium" /></a> I have been extremely impressed by Sync Framework 1.0 and Sync Framework 2.0, and I must say that Sync Framework 2.0 has really simplified the synchronization process beyond the Local Database Cache implementation pattern made famous in MSF 1.0. If you are interested in the Sync Framework, check out the Sync Framework dev center here: <a title="http://msdn.microsoft.com/en-us/sync/default.aspx" href="http://msdn.microsoft.com/en-us/sync/default.aspx">http://msdn.microsoft.com/en-us/sync/default.aspx</a></p> <p>In addition, my friend and former colleague Rituraj Singh co-authored a gem of a book, <a href="http://www.apress.com/book/view/9781430210054">Pro Sync Framework</a> which covers v1 of the Sync Framework and went a long way to get me started. </p> <p>The team is split between resources in Phoenix and the D.C. area, and I've been racking up my miles with US Airways flying out to D.C., on average once a month. My client has really embraced agile values which is just fantastic, and it is always nice to know I'll be keeping my Silver status :-)</p> <p>So, needless to say, this project is keeping me plenty busy so if I don't blog as often as I should over the next not so lazy days of summer, you'll know why. That said, here's what else I'll be up to over the next couple of months:</p> <p><strong>Phoenix Connected Systems User Group 1 Year Birthday, August 13th</strong></p> <p>1 year ago in August, my good friend Todd Sussman and I started the PCSUG. We've had some fantastic talks, covering BizTalk Server, WF, WCF, REST, .NET Services, and several discussions on SOA. So, to celebrate, we're throwing a party and you're invited! Stay tuned to <a title="http://www.pcsug.org/Home/Events" href="http://www.pcsug.org/Home/Events">http://www.pcsug.org/Home/Events</a> for more info on the August meeting which at a minimum will include pizza, sodas and cake to celebrate. You can also look out for the #PCSUG hashtag on twitter for more info.</p> <p><strong>SQL Server Worldwide User Group Virtual Conference, November 2009</strong></p> <p>I've been invited back to speak at the SSWUG VCon in the fall. I am currently working on my abstracts, but I'll announce my session topics sometime in the next few weeks. Of course, they will in some way involve WCF and very likely some Azure stuff.</p> <p><strong>New Article on Azure Compute and Table Storage Services in CoDe Magazine, September 2009</strong></p> <p>Look for a new article in the Sept/Oct issue of CoDe Magazine on Azure Compute and Table Storage. More details coming soon.</p> <p><strong>Reading List</strong></p> <p>What would summer be without a good reading list? Here are the books I plan to conquer this summer, in no particular order:</p> <ul> <li>The Art of Unit Testing by Roy Osherove </li> <li>Restful .NET by John Flanders </li> <li>Effective C# by Bill Wagner </li> <li>More Effective C# by Bill Wagner </li> <li>Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries 2nd Edition by Brad Adams, et al. </li> <li>Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions, Gregory Hohpe, et al. </li> </ul> <p>Well, that's all for now. Would love to hear what you are up to this summer- drop me a note.</p><img src="http://rickgaribay.net/aggbug/248.aspx" width="1" height="1" /> Rick G. Garibay http://rickgaribay.net/archive/2009/07/06/not-so-lazy-days-of-summer.aspx Tue, 07 Jul 2009 04:52:09 GMT http://rickgaribay.net/archive/2009/07/06/not-so-lazy-days-of-summer.aspx#feedback http://rickgaribay.net/comments/commentRss/248.aspx http://rickgaribay.net/services/trackbacks/248.aspx Persistent Digital Archives and Library System (PeDALS) http://rickgaribay.net/archive/2009/03/27/persistent-digital-archives-and-library-system-pedals.aspx <p>My good friend and colleague Todd Sussman and I have been working with the Arizona State Library who are leading an effort on behalf of the <a target="_blank" href="http://www.digitalpreservation.gov/partners/states_az/states_az.html">Library of Congress</a> to design, develop and deploy an automated, integrated workflow to process collections of digital publications and records for the <a href="http://www.digitalpreservation.gov/partners/states_az/states_az.html">Library of Congress</a>. Actually, Todd has been working on this great project for a while now and has only recently let me join in on the fun :-)<a target="_blank" href="http://rpm.lib.az.us/pedals/Pilot_Architecture.asp"><img style="MARGIN: 10px" align="left" width="386" height="292" alt="" src="http://www.pedalspreservation.org/Images/PeDALS_Pilot_Architecture-(v2-simple)Small.jpg" /></a></p> <p>The project is called Persistent Digital Archives and Library System (PeDALS), and the goal of the <a href="http://www.digitalpreservation.gov/partners/states_az/high/az_brochure_final0209.pdf">PeDALS</a> project is to both revolutionize and standardize the manner in which official document records are digitally archived.</p> <p>At its core, PeDALS aims to become both a long-term service to the national archive community and to local and national citizens alike. </p> <p>For archivists, the vision is to support the ability to ingest "digital stacks" of digital copies of documents and corresponding metadata from various offices of origin, parse and catalog the documents and metadata, store a “local” copy of the documents and metadata, and then replicate the archived document across 7+ nationally distributed repository clusters. We are leveraging BizTalk Server as the metadata splitter and archive broker for archiving the digital records to a highly replicated storage network that can preserve the authenticity and integrity of the collections indefinitely.</p> <p>Once the first phase (replicated dark storage) is complete, patrons like you and I can go to a public website and search on historical records like marriage certificates, official government documents, and even emails sent from government officials!</p> <p>Today, there are 5 participating states in the project, including Arizona, Florida, South Carolina, New York, and Wisconsin.</p> <p>Even more impressive, Microsoft Connected Systems technologies like BizTalk and .NET along with LINUX and BSD systems are driving national standardization of how the entire nation can work with a variety of repositories in a standards-compliant, interoperable manner to support the ongoing development of the system and promote best practices across national archive repositories.</p> <p>You can see an overview of the project here: <a href="http://www.digitalpreservation.gov/partners/states_az/states_az.html">http://www.digitalpreservation.gov/partners/states_az/states_az.html</a> as well as a system architecture diagram here: <a href="http://rpm.lib.az.us/pedals/Pilot_Architecture.asp">http://rpm.lib.az.us/pedals/Pilot_Architecture.asp</a>. </p> <p>All of this work is public record and I personally feel very proud to be working on this project as it will provide a great service to our local and national communities that will impact my children and several generations to come.</p><img src="http://rickgaribay.net/aggbug/233.aspx" width="1" height="1" /> Rick G. Garibay http://rickgaribay.net/archive/2009/03/27/persistent-digital-archives-and-library-system-pedals.aspx Sat, 28 Mar 2009 04:53:22 GMT http://rickgaribay.net/archive/2009/03/27/persistent-digital-archives-and-library-system-pedals.aspx#feedback http://rickgaribay.net/comments/commentRss/233.aspx http://rickgaribay.net/services/trackbacks/233.aspx