You are here

planet code4lib

Subscribe to planet code4lib feed
Planet Code4Lib - http://planet.code4lib.org
Updated: 1 hour 41 min ago

Karen Coyle: Floor wax, or dessert topping?

Tue, 2016-01-12 19:57
As promised, my book, FRBR: Before and After, is now available in PDF as open access with a CC-BY license. I'd like to set up some way that we can turn this into a discussion, so if you have a favorite hanging out place, make a suggestion.

Also, the talk I gave at SWIB2015 is now viewable on youtube: Mistakes Have Been Made. That is a much shorter (30 minutes) and less subdued explanation of what I see as the problems with FRBR. If that grabs you, some chapters of the book will give you more detail, and the bibliography should keep anyone busy for a good long time.

Let me be clear that I am not criticizing FRBR as a conceptual model of the bibliographic universe. If this view helps catalogers clarify their approach to cataloging problems, then I'm all for it. If it helps delineate areas that the cataloging rules must cover, then I'm all for it. What I object to is that implication that this mental model = a data format. Oddly, both the original FRBR document  and the recent IFLA model bringing all of the FR's together, are very ambiguous on this. I've been told, in no uncertain terms, by one of the authors of the latter document that it is not data model, it's a conceptual model. Yet the document itself says:
The intention is to produce a model definition document that presents the model concisely and clearly, principally with formatted tables and diagrams, so that the definitions can be readily transferred to the IFLA FRBR namespace for use with linked open data applications.  And we have the statement by Barbara Tillett (one of the developers of FRBR) that FRBR is a conceptual model only:
"FRBR is not a data model. FRBR is not a metadata scheme. FRBR is not a system design structure. It is a conceptual model of the bibliographic universe." Barbara Tillett. FRBR and Cataloging for theFuture. 2005This feels like a variation on the old Saturday Night Live routine: "It's a floor wax. No! It's a dessert topping!" The joke being that it cannot be both. And that's how I feel about FRBR -- it's either a conceptual model, or a data model. And if it's a data model, it's an entity-relation model suitable for, say, relational databases. Or, as David C. Hay says in his 2006 book "Data Model Patterns: A Metadata Map":
Suppose you are one of those old-fashioned people who still models with entity classes and relationships.It's not that entities and relations are useless, it's just that this particular style of data modeling, and the technology that it feeds into, has been superseded at least twice since the FRBR task group was formed: by object-oriented design, and by semantic web design. If FRBR is a conceptual model, this doesn't matter. If it's a data model -- if it is intended to be made actionable in some 21st century technology -- then a whole new analysis is going to be needed. Step one, though, is getting clear which it is: floor wax, or dessert topping.

Ariadne Magazine: #Ukmedlibs

Tue, 2016-01-12 18:57

Tom Roper, Sam Burgess and Holly Case discuss the formation, use, benefits and limitations of Twitter chat sessions for forming and maintaining professional networks. They focus on the #ukmedlibs chat aimed at UK (and European) health library professionals, which has been running since May 2015.

Read more about #UkmedlibsIntroduction Twitter chats offer a new way to undertake professional development and networking online.  A Twitter chat takes place at a pre-arranged time, uses a hashtag to organise and aggregate tweets, and usually tackles an agenda of numbered questions.   

Tom Roper, Sam Burgess and Holly Case. All correspondence to tom.roper@bsuh.nhs.uk

Organisations: Article type: Issue number: Authors: Date published: Tue, 01/12/201675http://www.ariadne.ac.uk/issue75/roper-et-al

Villanova Library Technology Blog: eBook available: How to Be a Detective

Tue, 2016-01-12 18:27

Our latest eBook release, produced with the help of Distributed Proofreaders, is another of Frank Tousey‘s Ten Cent Hand Books, though a rather unusual one.

Attributed to fictional detective Old King Brady, hero of the Secret Service series, How to Be a Detective consists primarily of a series of short stories designed to illustrate different aspects of detective work, with the overall moral being that you can’t learn detective work from a book, and that most people simply aren’t cut out for it. While the book does not really deliver on the promise of its title, it does serve as an interesting example of the intersection between fiction and non-fiction in the dime novel era.

The entire text of the book may be read online or downloaded through Project Gutenberg.


Like0

Villanova Library Technology Blog: The Highlighter: Have You Discovered Your Virtual Book Bag?

Tue, 2016-01-12 18:06

This video shows how to create a temporary list of books, without having to log in, which can then be saved, emailed, exported or printed:


For additional “How to” videos, click the “Help” button on Falvey’s homepage.


Like0

Ariadne Magazine: Ariadne is not the only fruit

Tue, 2016-01-12 17:48

John Kirriemuir, editor of the first ten issues of Ariadne, reminisces about library and information science e-­journals back in the day, looks across the current landscape of online “free to read, free to write for” publications, considers a few questions for budding authors to ask, and highlights some publications to house their words.

Read more about Ariadne is not the only fruit
In the beginning there was the Jisc­-funded buffet  Article type: Issue number: Authors: Date published: Tue, 01/12/201675http://www.ariadne.ac.uk/issue75/kirriemuir

Ariadne Magazine: Events: OER16: Open Culture

Tue, 2016-01-12 16:36

Lorna M. Campbell introduces the Open Educational Resources Conference 2016 (OER16). This will be held in April at the University of Edinburgh in Scotland, and will focus on the theme of "Open Culture". Participants will be looking at how open culture can be embedded into institution's learning, teaching and research offerings.

Read more about Events: OER16: Open Culture

Lorna M. Campbell

Article type: Issue number: Authors: Organisations: Projects: Date published: Tue, 01/12/201675http://www.ariadne.ac.uk/issue75/campbell

Ariadne Magazine: Back to the moon - eLib and the future of the library

Tue, 2016-01-12 09:09

Martin Hamilton, Jisc's resident futurist and one time developer on the ROADS project in the 1990s, looks back at the heady days of the Follett Report, the eLib projects that appeared as a result and the services that some of them gave rise to. He then proposes an interesting long term archiving idea that might not be as far fetched as it sounds.

19th January 1996, and founding editor John Kirriemuir is about to hit “publish” on the first edition of Ariadne magazine Read more about Back to the moon - eLib and the future of the library

martin hamilton

Organisations: Article type: Issue number: Authors: Date published: Tue, 01/12/201675https://www.ariadne.ac.uk/issue/75/hamilton

SearchHub: Lucidworks Fusion 2.2 Now Available

Mon, 2016-01-11 19:51

Lucidworks Fusion 2.2 is now available for download!

Lucidworks is pleased to announce the release of Fusion 2.2. This is a preview release of new features and enhancements we have been working on.

Improved UI elements

We are continuously working on improving our interface and UX. The salient improvements in this release include:

  • Simplified home interface and panel management to get to where you need to be faster than ever.
  • Refined visual design to allow for increased information display.
  • Minimap navibar for smoother scrolling and/or quick jumps between open panels.
  • Full screen script editors for easier configuration.
  • Synonyms Manager with a new interface allowing for categorization and audit management of synonyms.

New Connectors

We have 3 new data source connectors.

Alfresco

The Alfresco connector adheres to the Content Management Interoperability Services (CMIS) standard and has been tested with the Alfresco Community 5.0.d edition

ServiceNow

The ServiceNow connector allows for the crawl/recrawl of SN records of type Problem, Incident and kb_knowledge.

ZenDesk

The ZenDesk connector retrieves tickets, metrics, comments and attachments from the popular customer support system. It retrieves all tickets with all fields (e.g., customer, assignee, priority, status) as well as access restrictions for users and groups. We have also made numerous under the hood enhancements addressing connector indexing performance, speed and stability.

More details can be found in the Fusion 2.2 Preview release notes.

So go ahead, and give our latest version a try!

The post Lucidworks Fusion 2.2 Now Available appeared first on Lucidworks.com.

FOSS4Lib Recent Releases: VuFind - 2.5.1

Mon, 2016-01-11 17:07
Package: VuFindRelease Date: Monday, January 11, 2016

Last updated January 11, 2016. Created by Demian Katz on January 11, 2016.
Log in to edit this page.

Minor maintenance release.

ACRL TechConnect: Doing Six Impossible Things Before Breakfast: An Approach to Keeping it User Centered

Mon, 2016-01-11 17:00

Keeping any large technical project user-centered is challenging at best. Adding in something like an extremely tight timeline makes it too easy to dispense with this completely. Say, for instance, six months to migrate to a new integrated library system that combines your old ILS plus your link resolver and many other tools and a new discovery layer. I would argue, however, that it’s on a tight timeline like that that a major focus on user experience research can become a key component of your success. I am referring in this piece specifically to user experience on the web, but of course there are other aspects of user experience that go into such a project. While none of my observations about usability testing and user experience are new, I have realized from talking to others that they need help advocating for the importance of user research. As we turn to our hopes and goals for 2016, let’s all make a resolution to figure out a way to make better user experience research happen, even if it seems impossible.

  1. Selling the Need For User Testing

    When I worked on implementing a discovery layer at my job earlier this year, I had a team of 18 people from three campuses with varying levels of interest and experience in user testing. It was really important to us that we had an end product that would work for everyone at all levels, whether novice or experienced researcher, as well as for the library staff who would need to use the system on a daily basis. With so many people and such a tight timeline building user testing into the schedule in the first place helped us to frame our decisions as a hypothesis to confirm or nullify in the next round of testing. We tried to involve as many people as possible in the testing, though we had a core group who had experience with running the tests administer them. Doing a test as early as possible is good to convince others of the need for testing. People who had never seen a usability test done before found them convincing immediately and were much more on board for future tests.

  2. Remembering Who Your Users Are

    Reference and instruction librarians are users too. We sometimes get so focused on reminding librarians that they are not the users that we don’t make things work for them–and they do need to use the catalog too. Librarians who work with students in the classroom and in research consultations on a daily basis have a great deal of insight into seemingly minor issues that may lead to major frustrations. Here’s an example. The desktop view of our discovery layer search box was about 320 pixels long which works fine–if you are typing in just one word.  Yet we were “selling” the discovery layer as something that handled known-item searching well, which meant that much of a pasted in citation wasn’t visible. The reference librarians who were doing this exact work knew this would be an issue. We expanded the search box so more words are visible and so it works better for known-item searching.

    The same goes for course reserves, interlibrary loan, or other staff who work with a discovery layer frequently often with an added pressure of tight deadlines. If you can shave seconds off for them that adds up a huge amount over the course of the year, and will additionally potentially solve issues for other users. One example is that the print view of a book record had very small text–the print stylesheet was set to print at 85% font size, which meant it was challenging to read. The reserves staff relied on this print view to complete their daily work with the student worker. For one student the small print size created an accessibility issue which led to inefficient manual workarounds. We were able to increase the print stylesheet to greater than 100% font size which made the printed page easily readable, and therefore fix the accessibility issue for this specific use case. I suspect there are many other people whom this benefits as well.

  3. Divide the Work

    I firmly believe that everyone who is interested in user experience on the web should get some hands on experience with it. That said, not everyone needs to do the hands on work, and with a large project it is important that people focus on their core reason for being on the team. Dividing the group into overlapping teams who worked on data testing, interface testing, and user education and outreach helped us to see the big picture but not overwhelm everyone (a little Overwhelm is going to happen no matter what). These groups worked separately much of the time for deep dives into specific issues, but helped inform each other across the board. For instance, the data group might figure out a potential issue, for which the interface group would determine a test scenario. If testing indicated a change, the user education group could be aware of implications for outreach.

  4. A Quick Timeline is Your Friend

    Getting a new tool out with only a few months turnaround time is certainly challenging, but it forces you to forget about perfection and get features done. We got our hands on the discovery layer on Friday, and were doing tests the following Tuesday, with additional tests scheduled for two weeks after the first look. This meant that our first tests were on something very rough, but gave us a big list of items to fix in the next two weeks before the next test (or put on hold if lower priority). We ended up taking off two months from live usability in the middle of the process to focus on development and other types of testing (such as with trusted beta testers). But that early set of tests was crucial in setting the agenda and showing the importance of testing. We  ultimately did 5 rounds of testing, 4 of which happened before the discovery layer went live, and 1 a few months after.

  5. Think on the Long Scale

    The vendor or the community of developers is presumably not going to stop working on the product, and neither should you. For this reason, it is helpful to make it clear who is doing the work and ensure that it is written into committee charges, job descriptions, or other appropriate documentation. Maintain a list of long-term goals, and in those short timescales figure out just one or two changes you could make. The academic year affords many peaks and lulls, and those lulls can be great times to make minor changes. Regular usability testing ensures that these changes are positive, as well as uncovering new needs as tools and needs change.

  6. Be Iterative

    Iteration is the way to ensure that your long timescale stays manageable. Work never really stops, but that’s ok. You need a job, right? Back to that idea of a short timeline–borrow from the Agile method to think in timescales of 2 weeks-1 month. Have the end goal in mind, but know that getting there will happen in tiny pieces. This does require some faith that all the crucial pieces will happen, but as long as someone is keeping an eye on those (in our case, the vendor helped a lot with this), the pressure is off on being “finished”. If a test shows that something is broken that really needs to work, that can become high priority, and other desired features can move to a future cycle. Iteration helps you stay on track and get small pieces done regularly.

Conclusion

I hope I’ve made the case for why you need to have a user focus in any project, particularly a large and complex one. Whether you’re a reference librarian, project manager, web developer or cataloger, you have a responsibility to ensure the end result is usable, useful, and something people actually want to use. And no matter how tight your timeline, stick to making sure the process is user centered, and you’ll be amazed at how many impossible things you accomplished.

William Denton: STAPLR

Mon, 2016-01-11 16:38

Announcing STAPLR: Sounds in Time Actively Performing Library Reference. It is a live streaming sonification that turns the reference desks at York University Libraries into music.

Listen in the background for ambient awareness of what’s going on at our desks—and for some beautiful moments that emerge when the simple composition currently running is applied to the unpredictable desk activity.

(I’ve had some reports from people who say it doesn’t work, but I don’t have enough details to debug the problem, so if the in-browser player doesn’t work, try the direct audio link, or try both in another browser. Requires Ogg Vorbis, so make sure your browser can handle that audio format. If the seconds are passing, it’s working, even if there’s no music: there may be nothing happening at the desks. If none of that works, please tell me your operating system and browser, and confirm you tried the direct audio link. Thanks.)

New composition coming soon, and an event in February. Technical details to follow too.

Open Knowledge Foundation: The Open Data Utopia of the Pampas

Mon, 2016-01-11 15:14
An Ad Hoc Introduction to Argentine Affairs

This post was written by Andres Snitcofsky an open government / data activist in Argentina. See Andres Medium account for more posts – https://medium.com/@rusosnith

Since a new government took office in Argentina, a party alliance called #Cambiemos (Let’s Change), a lot of things have changed. Less than one month has passed, and a lot of new directives (more than 40, some of them of the Urgent & Necessity kind) have been passed by the new administration.

Since the congress will reopen only in March, and the judiciary system is on leave until February, most of the announcements and deep political changes have been issued as government official orders: Decretos. This implies that these changes are instant, but those directives could be challenged by the legislative branch later this year (and they probably will be).

The Decretos thing may not be so important to foreign readers, but most of the #Cambiemos campaign was based on the premise of being respectful to the Republic Institutions, meaning to go “by the book” and to legislate bills about important topic in a democratic way.

Now, during the warm months of the southern summer, a philosophical debate arises: Form vs content. End goal vs means. Decree vs Debated Law.

This debate crosses the political spectrum that goes from the fanatics of the former government, now turned ‘opposition’, and the ones from the new administration, now ‘officials’. This debate does not discriminate and embraces almost all current political events.

Looking back

The Macri administration presents itself as The One who will bring order and light into the state. With only one month in office, and during the summer recess, they already started revising previous contracts with private enterprises, laws regarding the telecommunication monopolies, and firing lots of employees that were contracted in precarious and almost illegal ways by the state. If the previous administration had had better transparency and openness, we could be controlling how much of this “tidying up the mess” process is real thing, or if it’s just an excuse for lowering the state budget and adding even more precarization of the job market. It is not wise to hand over a state administration with lot’s of hidden numbers and unknown indexes, as it gives free play to the next in office to blame “la pesada herencia” (the heavy legacy) of the last one in charge, and do whatever they want with the excuse of fixing previous mistakes.

Crude example: As the inflation index since 2007 have been untrustworthy, the new government will need some time to build a good one. Till then, we won’t have even a fake one. And it will probably be the highest inflation times of the last two decades.

The Open Data Scene

This debate definitely didn’t skip the vibrant Argentinean open data community that just encountered its living example of the aforementioned dilemma:

Hoy estamos firmando un decreto que da inicio a construir un Gobierno Nacional Abierto. pic.twitter.com/Wc3RBmV0ri

— Andrés Ibarra (@andreshibarra) January 5, 2016 Translation: “Today we signed a decree which is the starting point of a National Open Government”

The Modernization Minister announced this week that the new government is willing to move forward in the Open Government agenda, including Open Data portals and policies, open contracting and more open initiatives. How this agenda has been promoted? Of course, with a governmental official order, or Decreto.

Some will say that it’s just espejitos de colores (Spanish expression similar to ‘snake oil’), or that it’s just a gesture to make the open data fans happy. However, we cannot deny former experience of the new national administration: As the City of Buenos Aires government, they created one of the most advanced policies in the country related to open data. They built an egov initiative, they assembled a really innovative GovLab, and developed lots of open data and online citizen participation tools. If we compare Buenos Aires City to the rest of the cities and even the national level, it ranks at the top. However, if we compare the openness of Argentina with the rest of Latin America, we end up in a really bad position. And that’s even if we only compare ourselves to our smaller surrounding countries of Bolivia, Chile, Paraguay and Uruguay, usually thought to be behindhand.

Currently, Argentina doesn’t have a Freedom of Information Law, or anything alike. The ruling party for the last 12 years has had plenty of commitments on their hands, but implemented just a few, and with little to no real empowerment. The only decree, signed in 2003 by Nestor Kirchner, lacked of political support and ended up being a bureaucratic path for those willing to question our government for access to public information. Most of those who tried filling a Information Request were even turned down. We are talking about asking basic information about your own country, through the channels built to do so, and not receiving a reply back. Or even worst, receiving one that’s almost satirical:

The President office in 2013, replying La Nacion’s Journalist @colmanromi that “the President’s salary datasheet wasn’t updated yet” when they erased one column of it to hide the actual salary.

For the last few years we didn’t even knew the poverty level.

We also signed up the Open Government Partnership, and tried to comply with a first action plan that was never fulfilled. In 2015 a new action plan was written, but it was not an action plan that was approved by the local CSOs. This has also been reflected in Global Open Data Index built by OKI and we can also (proudly for Mor Rubinstein) guess that the Minister is also looking at it:

La Argentina está en el puesto 54 en el ranking de apertura de datos públicos. Nuestro objetivo es estar entre los 10 primeros del mundo.

— Andrés Ibarra (@andreshibarra) January 5, 2016 “Argentina is in the 54 position in the open public data ranking. Our objective is to be in the top ten of the world”

 

Andres Ibarra, the Modernisation Minister, expresses his wishes to get into the top ten open countries in the world, at least in the Global Open Data Index. Even though this is not a vanity contest, we all share his wish to overcome years of delays and obscurantism. We know that the new government has lots of good, talented people pushing into the Open Side of the Force, not only in the technical but also in the political levels. However, we also know that the main party leading the #Cambiemos alliance has lots of politicians relying their power in non-open contracts, opaque ways of working and occluded information. That’s why we are happy with these announcements about moving into the openness, mostly because it demonstrates the political will of pushing forward an Open Government agenda, and because they are putting it out in the open, for everyone to learn about it (not only the NGO’s, CSO’s and nerds). But we are still suspicious about how much will actually change

a badge worn by CSO’s activists in OGP Summit 2015 in Mexico

 

 

That is also why we should keep pushing for a Free Access to Information Law to be discussed and legislated in the congress. Because a government order may be a good starting point, but we need something that makes transparency and openness a must, in all levels of the state and territory as well as something valued not just by the Presidency and his decrees but valued by the Argentine government as a whole. That’s why we should use this new momentum to show to the rest of our society how important this is. How it can help to fight corruption, improve participation, discover and implement best practices and even build jobs around opened data. Happily, inside the recently elected new congress, we have new voices pushing for a FOIA law, which will join the former ones and maybe bill it this year.    

Y vamos por ley de acceso a la información para que pueda imitar todo el Estado esta buena iniciativa del gobierno. https://t.co/vdpGpQ23HS

— Karina Banfi (@KBanfi) January 6, 2016 Deputy Karina Banfi (Cambiemos) tweet supporting FOI policies

Looking forward

We should support the sectors of the new administration that are willing to push forward the Open Data and OpenGov movement. We should also keep an eye on them, using the same tools they are giving us. We should keep fighting for a real Access to Information Law , and when the discussion gets into the law making machinery, we as civil society must continue to participate and make our voices be heard.

But most of all, we should keep spreading the word with our colleague citizens, sharing the pros and cons of this Open movements, teaching about privacy concerns and limits, helping them not to be afraid, and willing to use all of this openness to let the government know that we will be watching them!

Here is where I start thanking Mor Rubinstein and for Anca Matioc being my editors in this post and end up inviting all of you to share your opinion on the subject, my point of view, or both.

Islandora: New Islandora Collection: FJM Photo Archive

Mon, 2016-01-11 14:17

One of our favourite Islandora community sites, Fundación Juan March, has just launched an amazing new online collection of photographs. We had a close look at their collections and how the sight came together with a Show & Tell back in November 2014.

This new repository contains 7,500 photographs, dating back to 1955  and includes nearly 4800 names of individuals and entities. There are two main blocks: The first block includes representative images of the work of the Foundation from 1955-1974. The second block, from 1975, is mainly photographs taken at the headquarters in Madrid and in the museum in Cuenca and Palma. It includes pictures of artists like Hockney, Motherwell, Miró; composers such as Mompou, Halffter, Luis de Pablo and intellectuals like Garcia Marquez, José Luis Sampedro, Alberti, Severo Ochoa... and many many more.

The Photo Archive is aninterdepartmental project, coordinated by the FJM Library, together with Exhibitions, Music, Lectures, Brand-Communications & Experience.

LITA: Brave New Workplace: Your Homegrown CRM

Mon, 2016-01-11 12:02
A CRM empowers you to find connections between your users/patrons.

What is a CRM? For starters, an excellent starting point for this installment of Brave New Workplace. A CRM is a Customer Relationship Management database, a record management system comprised of different record levels from individual to organization, with entries and fields for interactions and transactions and notes. CRMs provide essential business intelligence to a company, nonprofit, or even (you guessed it) library.

As a new hire, you may feel overwhelmed by the amount of information you receive at first. A CRM can help you organize information by contact, associating workflows, projects, committee information, research interests and more with the relevant colleague. By categorizing and tagging colleagues, you can identify overlaps of interest and synergies.

CRMs are used for a variety of purposes, including communications automation and e-commerce. For our purposes, I suggest treating it as an repository resource, where your contacts and their research interests, collection needs, important emails and documents, and personal notes can be organized and stored. You can also use it to export reports and gauge your own performance. This is a powerful tool to have when you come on-board at a library, and when you organize your thoughts around your workplace relationships, you may find it easier to identify collaborators in interdepartmental efforts.

Example: When you meet a new librarian from Wake Forest at a conference, you can tie their individual record to that institution, and when they accept a position at UNC, you can record that move in your CRM while still having the history of what came before.

Many CRMs are designed with large-scale enterprise in mind- unless your library or department is looking to adopt a system, you’ll want to steer clear of these solutions which were designed with multiple data entrants and a system administrator in mind. It’s also important to remember that because CRMs are designed for a sales environment, some of the terminology (including customers) may seem at first glance inappropriate. Don’t let the standard terminology deter you from taking advantage of a powerful tool.

Capsule CRM

For myself, and for you, I’d suggest a single-user cloud-based CRM. You have a few options to choose from, many designed with social media integration in mind. I have been using Capsule since I began work at the University of Houston. It’s mobile friendly- always handy in meetings with vendors or when traveling at conferences.

You could also consider Radium, Humin, or ZOHO CRM. Pick what strikes your fancy! Be aware that as with all “free” options on the internet, it may eventually move to a paid model.

Capsule has easy options for importing CSV files of contacts, which I exported from both my Outlook email and my LinkedIn contacts. In addition, individual records can be entered by hand. As a general rule, I’d suggest a big upload of your contacts to start, with individual entry as an ongoing means of managing and cleaning your database.

Search and Find by Any Text Entry

Think of a CRM as a complement to any collaborative organizational project management tools you may use. A CRM can allow you to save important emails, notes, and project information to individual contact records.

Tasks in my CRM

Perhaps the greatest benefit of the CRM is the ease with which I can attach vendor contacts to a central vendor account. Essentially, being able to have all my Ebsco contacts in an Ebsco folder, with their titles and my notes, is the gift that keeps on giving.

Ebsco Account Record in my CRM

Another benefit of Capsule is that it is free for up to two “users,” which means that I can share access to my vendor contacts through a general login. This gives others the opportunity benefit from the CRM, and makes the CRM additionally functional as a sort of shared rolodex.

The more time you spend within your CRM, the more you’ll be able to tweak its functions and categories to make them useful. If you let a CRM languish, its information will soon become out-of-date. Remember, your data is only as good as your data management!

Here we are at the end of my Brave New Workplace series, and I hardly know how to end it. It’s been an awesome experience learning and hearing from all of you, LITA Blog readers. As we all continue to grow and learn in our respective workplaces, I hope to update and return to this series with ongoing suggestions. Thank you for your support! Tech on!

 

 

LibUX: 031 – 2016 Trends for Library Web Design

Mon, 2016-01-11 05:39

Our first podcast of the new year kicks off with our predictions for trends in library web design. We’re stoked to see how we tally-up at the end of the year. What do you think?

  1. 2:19 – “Service Design” will be the new “User Experience Design”
  2. 4:39 – the future of WordPress is JavaScript
  3. 5:07 – the library app is finally dead – moreover the app in general as something distinct from the web will bottom-out its unpopularity
  4. 9:41 – more predictive / anticipatory services
  5. 12:16 – maturing API Driven Design (inspired by Tim Broadwater)
  6. 15:54 – web animation everywhere you look (follow Rachel Nabors)
  7. 16:51 – #libweb drops the carousel, embraces the gigantor hero-unit search
  8. 19:12 – design around time, as in just-in-time information
  9. 20:11 – the market for prototyping tools explodes
  10. 22:18 – Slack. Just Slack.

If you like you can download the MP3.

You can subscribe to LibUX on Stitcher, iTunes, or plug our feed right into your podcatcher of choice. Help us out and say something nice. You can find every podcast on www.libux.co.

The post 031 – 2016 Trends for Library Web Design appeared first on LibUX.

Terry Reese: MarcEdit Update (all versions)

Mon, 2016-01-11 04:39

I decided to celebrate my absence from ALA’s Midwinter by doing a little coding.    I’ve uploaded updates for all versions of MarcEdit, though the Mac version has experienced the most significant revisions.  The changes:

Windows/Linux ChangeLog:

OSX ChangeLog:

You can get the update from the Downloads page (http://marcedit.reeset.net/downloads) or using the automated updating tools within MarcEdit.

Questions,

–tr

Terry Reese: MarcEdit Mac: Verify URLs

Mon, 2016-01-11 04:36

In the Windows/Linux version — on of the oldest tools has been the ability to validate URLs.  This tool generates a report providing the HTTP status codes returned for URLs in a record set.  This didn’t make the initial migration  — but has been added to the current OSX version of MarcEdit.

To find the resource, you open the main window and select the menu:

MarcEdit Mac: Main Window Menu — Verify URLs

Once selected, if works a lot like the Windows/Linux version.  You have two report types (HTML/XML), you can define a title field, you can also set the fields to check.  By default, MarcEdit selects all.  To change this — you just need to add each new field/subfield combination in a new line.

MarcEdit Mac: Verify URLs screen

Questions, let me know.

–tr

Terry Reese: MarcEdit Mac: Edit 006/008 data

Mon, 2016-01-11 04:30

One of the functions that didn’t make the initial migration cut in the MarcEditor was the ability to edit the 006/008 in a graphical interface.  I’ve added this back into the OSX version.  You can find it in the Edit Menu:

MarcEdit Mac — Edit 006/008 Menu Location

Invoking the tool works a little differently than the windows/linux version.  Just put your cursor into the field that you want to edit, and the select Edit.  MarcEdit will then read your record data and generate an edit form based on the material format selected (or the material format from the record if editing).

MarcEdit Mac — Edit 006/008 Screen

Questions — let me know.

–tr

Patrick Hochstenbach: Sktchy Portraits

Sun, 2016-01-10 19:34
Filed under: Figure Drawings, Sketchbook Tagged: art, comic, fountainpen, mixed media, Photoshop, portrait, twsbi

Terry Reese: Build New Field Enhancements

Sun, 2016-01-10 05:17

Couple of interesting questions this week got me thinking about a couple of enhancements to MarcEdit.  I’m not sure these are things that other folks will make use of often, but I can see these being really useful answering questions that come up on the listserv.

The particular question that got me thinking about this today was the following scenario:

The user has two fields – an 099 that includes data that needs to be retained, and then an 830$v that needs to be placed into the 099.  The 830$v has trailing punctuation that will need to be removed. 

Example data:
=099  \\$aELECTRONIC DATA
=830  \\$aSeries Title $v 12-031.

The final data output should be:
=099  \\$aELECTRONIC RESOURCE 12-013
=830  \\$aSeries Title $v 12-031.

With the current tools, you can do this but it would require multiple steps.  Using the current build new field tool, you could create the pattern for the data:
=099  \\$a{099$a} {830$v}

This would lead to an output of:
=099  \\$aELECTRONIC RESOURCE 12-031.

To remove the period – you could use a replace function and fix the $a at the same time.  You could have also made the ELECTRONIC RESOURCE string a constant in the build new field – but the problem is that you’d have to know that this was the only data that ever showed up in the 099$a (and it probably won’t be).

So thinking about this problem, I’ve been thinking about how I might be able to add a few processing “macros” into the pattern language – and that’s what I’ve done.  At this point, I’ve added the following commands:

  • replace(find,replace)
  • trim(chars)
  • trimend(chars)
  • trimstart(chars)
  • substring(start,length)

The way that these have been implemented – these commands are stackable – they are also very ridged in structure.  These commands are case sensitive (command labels are all lower case), and in the places where you have multiple parameters – there are no spaces between the commas. 

So how does this work – here’s some examples (not full patterns):
{099$a.trim(“.”)}
{050$b.replace(“1950”,”1980”).trim(“.”)}
{LDR.substring(6,1)}

As you can see in the patterns, the commands are initialized by adding “.command” to the end of the field pattern.  So how we would apply this to the user story above.  It’s easy:
=099  \\$a{099$a.replace(“DATA”,”RESOURCE”)} {830$v.trimend(“.”)}

And that would be it.  With this single pattern, we can run the replacement on the data in the 099$a and trim the data in the 830$v. 

Now, I realize that this syntax might not be the easiest for everyone right out of the gate, but as I said, I’m hoping this will be useful for folks interested in learning the new options, but am really excited to have this in my toolkit for answering questions posed on the listserv.

This has been implemented in all versions of MarcEdit, and will be part of this weekend’s update.

–tr

Pages