<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>A few things—North Carolina does have the contributing organizations sign an agreement with Duke University, I’ve just received that and will forward to the Steering Committee. It’s very very simple. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regarding Mountain West digital library, although it’s not something Ohio probably wants to do, they moved off CONTENTdm’s multi-server several years ago to ExLibris’s Primo, I think that’s what it’s called, which aggregates the results across a number of digital asset management systems. If you remember from way back in September we looked at the Mountain West model, which is a regional DPLA site which is aggregating from not only Utah and Nevada cultural heritage institutions but the Arizona Memory Project and Montana Digital Library which are CONTENTdm sites. Interesting that the two big Oregon universities may be going into Mountain West. I think that DPLA is encouraging individual institutions in the West to go to MWDL where their states aren’t moving to DPLA. I know that Colorado has been encouraged to look at going with them. Liz<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> DPLAsteering [mailto:dplasteering-bounces@lists.oplin.org] <b>On Behalf Of </b>Reese, Terry P.<br><b>Sent:</b> Wednesday, February 3, 2016 8:35 AM<br><b>To:</b> Stephen Hedges <stephen@oplin.ohio.gov><br><b>Cc:</b> dplasteering@lists.oplin.org<br><b>Subject:</b> Re: [DPLAsteering] Repox Discussion notes with the North Carolina Digital Heritage Project<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Oregon is joining the Mountain West project as an avenue for contributing content (at least, UO and Oregon State are). As a state, I think that is likely going to be the path forward. And if I remember correctly, the Mountain West uses CONTENTdm’s multi-site (or use to) to aggregate the metadata.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>--tr<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Stephen Hedges [<a href="mailto:stephen@oplin.ohio.gov">mailto:stephen@oplin.ohio.gov</a>] <br><b>Sent:</b> Wednesday, February 3, 2016 10:29 AM<br><b>To:</b> Reese, Terry P. <<a href="mailto:reese.2179@osu.edu">reese.2179@osu.edu</a>><br><b>Cc:</b> <a href="mailto:dplasteering@lists.oplin.org">dplasteering@lists.oplin.org</a><br><b>Subject:</b> Re: [DPLAsteering] Repox Discussion notes with the North Carolina Digital Heritage Project<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Very, very interesting, Terry. Also a little disturbing. I wonder how many of the state hubs are held together with duct tape like this?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We know New York is struggling with Repox. We know Pennsylvania is trying to put something together with Hydra. DPLA itself seems to be working on Hydra in a Box. What is Oregon doing?<o:p></o:p></p></div><div><p class=MsoNormal>--<br clear=all><o:p></o:p></p><div><div><div><div><p class=MsoNormal>Stephen<o:p></o:p></p></div><div><p class=MsoNormal>614-728-5250<o:p></o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Feb 3, 2016 at 9:39 AM, Reese, Terry P. <<a href="mailto:reese.2179@osu.edu" target="_blank">reese.2179@osu.edu</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Let me know if you have questions…..<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>****************************************************************************************<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i>Repox Discussion with Lisa Gregory and Stephanie Williams; North Carolina Digital Heritage Center</i></b><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Lisa Gregory; Interim Director<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Stephanie Williams; Programmer<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I had the opportunity to speak to members of the North Carolina Digital Heritage Center on 2/2/2016 – specifically around their implementation of Repox, the time it took initially for them to setup the project, and their long-term support with the project. Here are the highlights:<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>As an organization, the North Carolina Digital Heritage Center’s DPLA operations are run on a skeleton budget. When the NCDH joined the DPLA, they did it as an extension of their already existing program. They are funded by the State Library of North Carolina, have a mandate to support digitization and collection hosting, and are funded via the State Library and LSTA funds. When Jenn Riley began working with the DPLA as part of the pilot, the organization took the project on without additional funding (and still, to this day, runs in this capacity). This meant that the NCDH has made some very specific program decisions:<o:p></o:p></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in'>1.<span style='font-size:7.0pt'> </span>They don’t recruit content into their portal. They work with the people that are highly motivated and interested in the project. They also work with folks that are technically capable of working with them. If an institution doesn’t want to share their metadata, they won’t try to convince them. If an institution doesn’t have the technical capacity to share their collections, they may see if that institution would like the NCDH to take on hosting responsibilities – but generally, they accept content only from organizations that can provide them with a valid, easy to understand, OAI-PMH feed.<o:p></o:p></p><p style='margin-left:1.0in'>2.<span style='font-size:7.0pt'> </span>As an organization, they do zero (well, almost zero…they strip some data and add a field to identify the organization an item came from) metadata remediation, and require no remediation from their partners. There are two main areas of thoughts behind this:<o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>DPLA isn’t providing any funding to support metadata remediation at the Hub level – and given that this is something being done essentially by part-time staff, there just aren’t the resources. <o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>Repox does what it does well (creating a data aggregation), and doesn’t do much else. Organizations that have struggled with Repox have struggled because they have tried to shoehorn functionality like metadata remediation into their process. Repox doesn’t do that…easily. <o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>As a group, the NCDH felt that asking partners to change their metadata from past collections wasn’t sustainable. They provide their partners best practices, allow organizations to see the results of not having specific metadata when rendered in DPLA (i.e., if geographic headings are not standard, your content doesn’t show up in a geographic search) – but as an organization, they are a hands off metadata shop.<o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>They have no formal agreements with data partners. The NCDH works with members that ask to have their metadata aggregated. They do no education around what that means (CC0), and they assume that their partners understand the terms DPLA requires when making metadata available. As such, they don’t ask data providers to sign formal agreements.<o:p></o:p></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>Finally, I was interested in DPLA’s response to the lack of metadata remediation. Apparently, DPLA has spoken with them a number of times, but their attitude is that as long as they are maintaining the aggregation, DPLA will just have to live with what they get.<o:p></o:p></p><p style='margin-left:1.0in'>3.<span style='font-size:7.0pt'> </span>Technically, the NCDH utilizes Repox – specifically version 2.2.7 (this is the old development branch). <o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>They did note some trepidation around using repox. Apparently, there were a couple of years when no one was supporting it, and the project website disappeared. The new github page is new, and also based on a different architecture. This concerns them a little, but not enough to consider a technology switch. The minimal support work is what keeps them on the version they are using.<o:p></o:p></p><p style='margin-left:2.0in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>Information about the Repox Versions:<o:p></o:p></p><p style='margin-left:2.5in'><span style='font-family:"Courier New"'>o</span><span style='font-size:7.0pt'> </span>Version 2.2.7 – Java client/application with a LAMP backend.<o:p></o:p></p><p style='margin-left:2.5in'><span style='font-family:"Courier New"'>o</span><span style='font-size:7.0pt'> </span>Version 3.x – Java web application utilizing a LAMP backend with Jersey as the interface framework<o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>Initial setup:<o:p></o:p></p><p style='margin-left:2.0in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>NCDH noted that the initial up and running time for the project was approximately 4 weeks. This included developer time to work on the initial set of 6 XSLTs for the initial metadata harvests, and a system admin to get Repox running within their environment. <o:p></o:p></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:2.0in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>They run Repox on windows. They did this because they had significant trouble getting Repox secured on their Linux infrastructure. They didn’t elaborate – but the issue threatened to derail them, so they run Repox on a standalone windows server, only accessible by IP address by NCDH staff and the single DPLA harvester.<o:p></o:p></p><p style='margin-left:1.5in'><span style='font-family:Wingdings'>§</span><span style='font-size:7.0pt'> </span>Long-term:<o:p></o:p></p><p style='margin-left:2.0in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>Repox is managed as part of their normal infrastructure. The software is managed by their programmer, which said she spends ~1-2 hours a month with the program. A system admin just maintains the Windows Server.<o:p></o:p></p><p style='margin-left:2.0in'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt'> </span>New members take ~1 week programmer time to get ingested into the aggregation. This time is spent creating the XSLT that generates the MODs feed DPLA requests.<o:p></o:p></p><p style='margin-left:2.5in'><span style='font-family:"Courier New"'>o</span><span style='font-size:7.0pt'> </span>New members take ~2 weeks for the program manager, as she does the initial metadata discussions and profiling with the interested member.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Things that they had for us to think about:<o:p></o:p></p><p style='margin-bottom:12.0pt'>1.<span style='font-size:7.0pt'> </span>If DPLAOH wants to do anything beyond simply creating an aggregation, Repox may not be the best fix. It certainly has the lowest barrier to entry – but it does one thing very well, and that is about it. If we need to do more than that, we’ll find very quickly that we will be fighting with the toolset.<o:p></o:p></p><p>2.<span style='font-size:7.0pt'> </span>Repox long-term support is still up in the air. It’s definitely supported by Eurpeana and others – but in the time they have used it, 2/3 of that time, the project website simply disappeared. They’re biggest worry is that support may not be available long-term; especially for the development branch that they are most comfortable with as the 3.x branch would require more hands on treatment. What they like about the 2.2.7 branch is that it’s a completely self-contained application.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333'><img border=0 width=179 height=36 id="_x0000_i1025" src="cid:image001.png@01D15E65.65DAF010" alt="The Ohio State University"><br></span><b><span style='font-size:10.0pt;color:#BB0000;background:white'>Terry Reese</span></b><span style='font-size:10.0pt;color:#333333'><br>Head of Digital Initiatives<br></span><span style='font-size:10.0pt;color:#BB0000;background:white'>University Libraries</span><span style='font-size:10.0pt;color:#333333'> <br></span><span style='font-size:10.0pt;color:black'>320F 18<sup>th</sup> Avenue Library, </span><span lang=EN style='font-size:10.0pt;color:black'>175 West 18th Avenue</span><span style='font-size:10.0pt;color:black'>, Columbus, OH 43210<br><a href="tel:614-292-8263" target="_blank">614-292-8263</a> Office / <a href="tel:614-407-4998" target="_blank">614-407-4998</a> Mobile<br></span><span style='font-size:10.0pt;color:#333333;background:white'><a href="mailto:reese.2179@osu.edu" target="_blank"><span style='color:#0563C1'>reese.2179@osu.edu</span></a></span><span style='font-size:10.0pt;color:#333333'> / <span style='background:white'><a href="http://library.osu.edu/" target="_blank"><span style='color:#0563C1'>http://library.osu.edu</span></a> / <a href="http://reeset.net/" target="_blank"><span style='color:#0563C1'>http://reeset.net</span></a> </span></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal><br>_______________________________________________<br>DPLAsteering mailing list<br><a href="mailto:DPLAsteering@lists.oplin.org">DPLAsteering@lists.oplin.org</a><br><a href="http://lists.oplin.org/mailman/listinfo/dplasteering" target="_blank">http://lists.oplin.org/mailman/listinfo/dplasteering</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>