Category Archives: 2017

PresQT Conference

PresQT: presqt.crc.nd.edu

PresQT: presqt.crc.nd.edu

I have just returned from PresQT. This is an academic conference focused on preservation of digital data, especially scientific datasets and software. The point is to allow others to check results through reproducibility. I was invited to give the corporate perspective on preservation.

As I wrote several weeks ago in my post on innovation, I am not a fan of silos. Attending this conference I found another set of silos: academic and corporate. There were so many tools people were discussing that I had never heard of. The first day left me reeling from all the new information. I also felt WAY out of my depth. I was wondering why I was there, how I could contribute and how this effort could engage the corporate and law firm worlds.

I did my presentation relatively early in the morning on the second day and felt much more like I could contribute to the discussion. I was warmly welcomed, good things were said about my talk and people asked a lot of questions. This answered my question. Part of my presentation was about content strategy (see my posts on the components of a good content management plan), but another part was about how academia and corporate environments can work together on this project to achieve better, more useful results.

Part of my point was that preservation starts with a content strategy. Preserving at the end is great, but much can be lost if you don’t start from the beginning. Of course, nobody in corporate, law firms (law firms do have a good handle on records management for client files) or academia does this. Preservation is an after thought. Content management is a huge undertaking. I hope to make a difference, but it will be small as I am one person shouting about it into a canyon. Whatever small inroads I can make in my work will be worth it.

I learned a lot. I learned about new tools and sites. One is ReproZip, which allows people to backup and entire project “by tracing the systems calls used by the experiment to automatically identify which files should be included. You can review and edit this list and the metadata before creating the final package file. Packages can be reproduced in different ways, including chroot environments, Vagrant-built virtual machines, and Docker containers; more can be added through plugins. What this means to someone like me is that I can pack up my entire website and someone in the future will be able to unpack the whole thing and look at it in all of its glory. Software, databases, widgets, text, everything is included so that the project/site/whatever can run as it did when it was posted on the web. The difference between this and the Internet Archives Wayback Machine is that pieces can be missing from the Wayback Machine as their crawler can’t access everything. The downside of ReproZip is that the creator, or someone involved in the project or site, must create the archive. The ReproZip tool comes out of the NYU Center for Data Science. A librarian, Vicky Steeves, is heavily involved in the project as a trainer and outreach coordinator. It makes my librarian heart happy.

I was also very interested in Euan Cochrane’s Wikidata project. Wikidata, funded in part by the Wikimedia Foundation, is a free and open knowledge base that can be read and edited by both humans and machines. Wikidata acts as central storage for the structured data of its Wikimedia sister projects including Wikipedia, Wikivoyage, Wikisource, and others. As you know, I like the idea of central storage for information. I like wikis a lot and this platform allows all different people to edit and contribute. They do have reviewers to verify information.

The thing I like most about Code Ocean, aside from the name, is the look and feel. It is pretty and looks like it has a user interface that it easy to use. Code Ocean is a cloud-based executable research platform. I am sure that it works very well, too- I can’t really speak to that as it is out of my area of expertise. I hope we can make the PresQT tool look and feel just as good.

I also think that Code Ocean could create a section that would be useful for tech companies. They could deposit their code as a safeguard for changes to their corporate structure and backup as well as well historic preservation. So many companies with interesting tools have gone out of business as the tech industry waxes and wanes. Think about some of the early search engines. As a result we have lost that knowledge. What could be done with it if it were deposited somewhere like Code Ocean and made available once certain corporate events or actions took place?

The big coup, from my point of view, is learning about Open Science Framework. This is essentially a streamlined, but well thought out and useful content management system. One thing that is very intriguing is that it overlays (not sure if that is the right idea) on top of cloud based storage systems and allows users to search across them. I think this tool could solve the problem of companies using Box, DropBox and Google Drive. I have a lot to learn about it, but I hope to become more well versed and use it to its fullest extent. Stay tuned for more on OSF.

Just because I didn’t mention every single tool or presentation doesn’t mean that I didn’t find it interesting or potentially useful. There was so much interesting work shown at this event that I feel somewhat overwhelmed. I hope to be able to participate further.

EVERYONE can participate in PresQT in different ways. One is to take the needs assessment. This survey will allow the team to get feedback from more people to make the tool more useful. The permanent link will be available soon and I will post it here. Personally, I had a hard time with the survey as the language, and some of the subject matter, was not in my wheelhouse. Still, I soldiered on and provided as much helpful feedback from my community as I could.

People can also explore the resources from the conference on OSF. More of the presentations will be posted there shortly.

Thoughts on Innovation

I am very interested in innovation and how it relates to business practice. Recently I read an article called How Innovative is Your Firm, Really? from the Above and Beyond KM blog. While this is targeted at law firms, I see a lot of parallels with business in general. The 6 points outlined are a good way to judge the innovation at your firm or in your business. They are basic (as in anyone can understand them and relate to them), measurable and sensible.

Basic, measurable and sensible are 3 keys to success of any program. In this case, law firms have a better chance of succeeding with change if they think along these lines.

Purpose: “A clear, inspiring reason for the company to exist — beyond just making money.”  ‘ I think this is a difficult principle for law firms. I am not sure how many people have a burning desire to become lawyers for any other reason than making money. Those who want to help people and organizations go into public service and the money isn’t there. Higher ups in a law get to choose very worthwhile pro bono work, which is an added bonus. The law firm’s mission is a challenge. I think this point would probably be the hardest to formulate. I also think getting buy-in would be a challenge.

Experimentation: “Trying out new ideas and making evidence-based decisions about how to move forward.”   ‘ As a manager I always tried new tools and ideas to try and get the right mix of information out to people at the right time. Not every idea works, but failure (in the most positive sense of the word) is part of the process. The key is to encourage experimentation and also cut bait when something isn’t working. Stopping a trial is hard, especially when people have invested time and possibly money into a program. Rehashing the good and the bad so admin can learn from the trial is really important. It brings knowledge into the firm both about what works and doesn’t, but also about the culture of the firm, how long something takes to implement and other valuable lessons.

Vendors often need to be part of experimentation. They want the firm to buy a new product. I was keen to try new tools relevant to the practice. However, I found, over time, that the 30-day free trial wasn’t enough. We spent time with set up, or got a stripped down version. We had to manage logins or work could not be saved. Too much work for too little time. I was successful with some vendors in getting short term, relatively inexpensive contracts so we could try out the full version for 6 months. I often included clauses that allowed us to get out of the contract or get a full contract depending on how the trial went. It was win-win for us and the vendor. They got some money and potential for more. We got a better way to evaluate new tools.

Collaboration: “Working across business functions to approach opportunities and challenges from all angles.”  ‘ As you know, I am not a fan of silos. While this often comes out in content management projects, silos manifest in the form of departments as well. It is really important for the admin team to understand what each other does and how the departments can help each other. If there is no other reason, then a department manager can outsource something they are doing to an expert. IT can install software faster and more securely than a HR department team member. The library can set up news searches or find information about a potential client more efficiently than someone in finance who only logs on to Lexis once a month.  The same goes for partners who need extra tools or information. Collaboration also makes work more interesting and, dare I say, fun? People are social creatures, so collaborating can add a boost to morale.

Empowerment: “Providing a clear path to create change in all corners of the company by reducing unnecessary constraints.”   ‘ Empowerment in law firms is challenging. Management often wants to exert a level of control over everything that stifles creative ideas. Obviously, no firm wants everyone to go haring off in crazy directions, but providing a space for empowerment is a good breeding ground for ideas with potential. Be open to listening and hearing what even the most junior person has to say. I am sure even the mail department can provide insights into improving efficiency around shipping and receiving.

‘ Looking out: “Looking beyond the company’s walls to understand customers, technologies, and cultural shifts.”  ‘ Who is looking out? Is it the job of one person or department? Encourage everyone to look out and have a section on the Admin team meeting agenda where people bring things they saw or heard to the table. Ditto with the Management team. Allow people the space to give their opinion, both pro and con. This will also show management depths that employees have that they may not get to display in the normal course of their daily work. Actively discourage heckling or negativity regarding any ideas. Heckling and negativity will shift the power to those who do it and discourage others from participating. More importantly, management won’t get anything out of the exercise and the time will be wasted. This is an excellent case where “do unto others as you would have them do unto you” must be scrupulously enforced.

Refinement: “Elegantly bridging vision and execution.”  ‘ The proof is in the pudding. Ideas are great, but if you never bridge ideas into reality, then what is the point? Starting with smaller changes will give the firm experience on methodology and the effects of change. Also, the person with the idea may not be the best person to implement, but that person must still be part of the process. Evaluate your assets, especially in terms of people, and make temporary changes so that vision and execution are as smooth as possible.

I like to say that projects are iterative. Most organizations can’t get the perfect tool-program-policy perfect the first time. By putting something pretty great in place (putting up crap just to put something up can defeat the purpose of change) can get a new project rolling and inspire others to contribute to improving it.  With too many moving parts or too much change, programs will fail. By making small changes and working up to larger programs, the firm or business can make innovation a habit and part of the culture.

The article referenced comes about from Ideo and talks also about their “assessment and dashboard tool: Creative Difference.” I am interested in the general principles, so I haven’t, yet, reviewed Creative Difference, nor have I heard of any law firms using it. I am sure that law firms trying it out will be able to start to make the changes they need to make to avoid the coming law business crash.