Home » Academic Works (Page 4)
Category Archives: Academic Works
Academic Works at the CUNY IT Conference
The City University of New York’s 14th annual IT Conference was held at John Jay College on December 3rd and 4th. While a number of sessions addressed open access initiatives at CUNY, a few specifically highlighted the role of CUNY Academic Works as part of these efforts — from the preservation challenges presented by digital dissertations at the CUNY Graduate Center to the launch of a new open access journal devoted to the scholarship of teaching and learning in art history, Art History Pedagogy and Practice, that will be published in CUNY Academic Works.
On Friday afternoon, William Casari, Jill Cirasella, Miriam Deutch and Megan Wacha presented “Opening CUNY: Academic Works at Work.” This session introduced attendees to the repository initiative and discussed how opening content to the world impacts CUNY and its community, both local and global. In order to provide a sense of the range of content types collected by CUNY Academic Works, each speaker addressed a specific collection at their institution: dissertations at the Graduate Center, open educational resources (OERs) at Brooklyn College, the “Save Hostos” Gerald J. Meyer archival collection at Hostos Community College, and faculty research from across the entire City University of New York. Slides are available via CUNY Academic Works.
Woah, we’re halfway there
When CUNY Libraries embarked on the trail to a more open CUNY, the Office of Library Services communicated three actionable goals for the first 18 months:
- In 6 months, 50% of institutions will have at least one collection in the repository
- In 12 months, 100% of institutions will have at least one collection in the repository
- In 18 months, CUNY Academic Works will have 15,000 items representing diverse content types and disciplines
In just eight months since the goals were announced at the Academic Works kick-off this March, 100% of institutions have at least one collection in the repository, and (WOAH!) we’re already halfway to the 18 month goal. There are now over 7,500 items in CUNY Academic Works.
Open Trails
Back in November of 2011, the CUNY University Faculty Senate passed a Statement and Resolution on Open Access – a resolution which supported the establishment of a CUNY-wide open access institutional repository and which has been a guiding document in the development of that repository, from its collections policies to its mission and goals:
CUNY Academic Works is a service of the CUNY Libraries dedicated to collecting and providing access to the research, scholarship and creative work of the City University of New York. In service to CUNY’s mission as a public university, content in Academic Works is freely available to all.
CUNY Academic Works aims to:
- Provide centralized, public access to the scholarly and creative output of the students, faculty, and staff of the City University of New York.
- Promote research and collaboration within and between the twenty-four campuses that make up the City University of New York, as well as the larger public.
- Preserve the history and development of the City University of New York.
While the mission and goals of Academic Works are clearly stated, it’s understandable that the first steps to meeting them can feel a little uncertain. Therefore, in order to support the Libraries as we embark on the trail to a more open CUNY, the Office of Library Services communicated three actionable goals for our first 18 months:
- In 6 months, 50% of institutions will have at least one collection in the repository
- In 12 months, 100% of institutions will have at least one collection in the repository
- In 18 months, CUNY Academic Works will have 15,000 items representing diverse content types and disciplines
Sound familiar? OLS has been busy getting the word out about Academic Works since the kick-off this March, and, less than four months later, CUNY Libraries has met its first goal. In fact, we passed it. Thanks to the commitment and hard work of CUNY librarians, eighteen (count ’em, 18!) of twenty-four institutions have their first collections in the repository within four months. And these initial collections have us well on our way to meeting the 18 month goal; they include 2,500+ items spanning from traditional journal publications and monographs to data sets, student work, open educational resources, and archival collections that capture the history of the University.
CUNY enters the scholarly communication landscape at an exciting time. It’s a time that some find reminiscent of the wild west (and it certainly has its good, its bad, and its ugly), but it’s also a time in which CUNY has the opportunity to pioneer the way.
Behind OneSearch: Part 2 – View PNX and Source Records
In part two of this 3-part series about basic tools for understanding and troubleshooting results in OneSearch (Primo), you’ll find out how to view the PNX and also the source records “behind” search results. In part one, you learned about the structure of internal Primo records (PNX). In part three, we’ll show you how to use bookmarklets to easily view PNX and source records in one click.
Now that you understand Primo’s internal record structure, aka PNX (Primo Normalized XML), the next step is to learn how to view PNX. A small change to a Primo URL will allow you to view that PNX record for any record in Primo search results. For local data sources, such as Aleph and CUNY Academic Works, you can use the information in the PNX record to create a URL that will display the source data used to create that PNX record.
Primo PNX Record
Search for something in OneSearch
Pick a record in the results and click on the “Details” tab. Then click on the “open this item in a new window” icon at the top right of the “Details” frame:
(This opens the record in a full screen view.)
Copy this text:
&showPnx=true
Click anywhere in the address box:
Push the End key on your keyboard to move to the end of the URL, paste the copied text at the end of the URL, and hit the Enter key. The result looks like this:
(Click on the above image to see the result of “&showPnx=true” being added to a full screen search result display URL.)
Source Record: Aleph MARC
Now that you’ve got the PNX for an Aleph record, you can view the source MARC record in Aleph.
Examine the PNX that you opened. Near the top, you see fields like this:
<sourcerecordid>007651609</sourcerecordid>
<sourceid>CUNY_ALEPH</sourceid>
<recordid>CUNY_ALEPH007651609</recordid>
First of all, you know it’s an Aleph record because it says so in the sourceid field (CUNY_ALEPH). The sourcerecordid is the Aleph record number or “system number” (007651609).
Create that Aleph MARC record URL by placing that record number at the end of this base URL:
https://libsearch.cuny.edu/F?func=direct&doc_library=CUN01&format=001&doc_number=
For example:
https://libsearch.cuny.edu/F?func=direct&doc_library=CUN01&format=001&doc_number=007651609
This will take you to the OPAC MARC record view:
Source Record: Academic Works Dublin Core
If we look back at the search that we ran at the beginning of this post, we see that there was another record in the search result image and clicking on the “Details” tab for that record shows that it is from CUNY Academic Works:
Click in the full screen view URL/address box and add “&showPnx=true,” just as you did earlier. This will take you to this record’s PNX record and there you will be able to see the sourceid and sourcerecordid, just as we did for the Aleph record.
<sourcerecordid>jj_pubs-1019</sourcerecordid>
<sourceid>CUNY_BEPRESS</sourceid>
<recordid>CUNY_BEPRESSjj_pubs-1019</recordid>
(bepress is the vendor of the CUNY Academic Works software.)
To view Academic Works source data, we need a different (and longer) base URL:
http://academicworks.cuny.edu/do/oai/?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:academicworks.cuny.edu:
Otherwise, the process is the same. Take the sourcerecordid from the PNX record and add it at the end of the base URL. For example:
That was a lot for one post. But we have tools to make it easier: bookmarklets!
Coming soon:
