<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="/m/mpubs/styles/rss.css" ?>
<rdf:RDF 
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/"
>
    <channel rdf:about="http://quod.lib.umich.edu/w/weave/longfeed.xml">
        <title>Weave: Journal of Library User Experience</title>
        <link>http://weaveux.org</link>
        <description>Weave: Journal of Library User Experience</description>
        <items>
            <rdf:Seq>
				<rdf:li resource="https://doi.org/10.3998/weave.12535642.0003.105"/>
				<rdf:li resource="https://doi.org/10.3998/weave.12535642.0003.201"/>
				<rdf:li resource="https://doi.org/10.3998/weave.12535642.0003.202"/>
			</rdf:Seq>
        </items>
    </channel>
	<item rdf:about="https://doi.org/10.3998/weave.12535642.0003.105">
		<title>Download EPUB file for Volume 3, Issue 1</title>
		<link>http://hdl.handle.net/2027/spo.12535642.0003.105</link>
		<dc:creator> </dc:creator>
		<dc:date>2020</dc:date>
		<description>Download an EPUB file of Volume 3, Issue 1.</description>
		<prism:publicationName>Weave: Journal of Library User Experience</prism:publicationName>
		<prism:volume>3</prism:volume>
		<prism:number>1</prism:number>
		<prism:doi>https://doi.org/10.3998/weave.12535642.0003.105</prism:doi>
	</item>
	<item rdf:about="https://doi.org/10.3998/weave.12535642.0003.201">
		<title>Can User Experience Research Be Trusted? A Study of the UX Practitioner Experience in Academic Libraries</title>
		<link>http://hdl.handle.net/2027/spo.12535642.0003.201</link>
		<dc:creator>Robin Bergart</dc:creator>
		<dc:date>2020</dc:date>
		<description>This study was motivated by frustration with our work as user experience (UX) librarians in an academic library. Our job is to discover what our students and faculty need, want, and expect from the library. We explore their research and learning practices, and we examine how library services, resources, and spaces support these practices. This is enjoyable and often fascinating. We love talking to our users and observing their behaviors. But when it comes to applying our findings to improve the user experience, we run into problems. We rely on the skills and expertise of our library colleagues to implement many of our findings; however, they don’t always share our enthusiasm for UX research. Instead, they often challenge, reject, or just plain ignore our work, and as a result we aren’t able to make improvements and address user pain points.</description>
		<prism:publicationName>Weave: Journal of Library User Experience</prism:publicationName>
		<prism:volume>3</prism:volume>
		<prism:number>2</prism:number>
		<prism:doi>https://doi.org/10.3998/weave.12535642.0003.201</prism:doi>
	</item>
	<item rdf:about="https://doi.org/10.3998/weave.12535642.0003.202">
		<title>Structuring and Supporting UX Work in Academic Libraries</title>
		<link>http://hdl.handle.net/2027/spo.12535642.0003.202</link>
		<dc:creator>Shelley Gullikson</dc:creator>
		<dc:date>2020</dc:date>
		<description>Leah Buley wrote that user experience (UX) is “a famously messy thing to describe” (2013, p. 4). UX often describes the overall experience and emotions of a user as they engage in a service, product, or space. But UX can also be shorthand for UX research: the work done to understand the user and their experience. UX can also refer to UX design: the work done to create a good user experience, iterating improvements through UX research. In this paper, “UX work” may refer to UX research, UX design, or a combination of the two.</description>
		<prism:publicationName>Weave: Journal of Library User Experience</prism:publicationName>
		<prism:volume>3</prism:volume>
		<prism:number>2</prism:number>
		<prism:doi>https://doi.org/10.3998/weave.12535642.0003.202</prism:doi>
	</item>
</rdf:RDF>
