Student research conference concerns

From the Digital Commons Google group: 11/16/2016 by Meaghan Heselden <corbettm@email.gwu.edu>

For faculty and students who are concerned about the implications of publishing in the future, or about making their data publicly available before they've had the opportunity to submit a manuscript to a journal, we offer the option to embargo posters for a period of their choice (6 months up to 3 years). I've also pointed out the policies of several prominent health sciences journals and publishers that don't consider posters to be prior or duplicate publication, such as: 

- International Committee of Medical Journal Editors

- Sage Publishing

- PLoS 

- Nature Journals

We would advise our students to read individual journals' policies, and to contact the journal directly with any questions or concerns about their editorial process--we offer to assist with that, as well. 

Notes on administering an event community

The SEGue Event Community administration:

Event communities consist of Themes (years), Tracks (schedule), and Events (submissions), as well as Introductory Text and some documents (such as the program).

To create a new Theme:

Go to Configuration, Create new theme, Submit changes. It will bring you to a new page where you will add your theme title (2018), and if you want, a link to the English department and label, in the THEME CONFIGURATION section. Submit changes.

To create a new Track:

Go to the Configuration section of your new theme (2018), select Create New track. Submit changes. It will bring you to a new page where you will add your track title (schedule), and if you want, a link to the English department and label, in the TRACK CONFIGURATION section. Submit changes.

To assign events to a track:

Go to Manage Events. Click on an event title, go to Revise Event in the left sidebar. Check to see if there is a Session Title assigned and other things that need to be removed or added. For example, to place it in a specific order in the schedule, there needs to be a starting time assigned. Use a 24 hours format. An ending time is not required. Once you have looked at all the metadata (page information), then click SUBMIT at the bottom of the page, and choose Post in the left sidebar. Assign it to the correct track, and when you are all done, update the site.

How to revise an event that is already posted:

You can do this two ways. One would be to go to the Manage Events page, and choose the State: All events (the default will be Not Yet Posted). The easier way is to go to the (front end) schedule page (http://digitalcommons.brockport.edu/segue/2017/). Right click on the event title you want to revise so it opens in a new tab. Choose Edit Event. It takes you to the metadata page. Choose Revise Event in the left sidebar. Make your changes, click SUBMIT at the bottom of the page. Close the tab. Go back to the schedule page and do the same thing for the remaining events you want to revise. When you have revised everything you need, update all the levels (Update IR Event Community in sidebar). 

IITG MidYear Project Outcomes

Report Mid Year Project Outcomes

1)            Please consider the original timeline and deliverable targets. How is your project progressing compared with the original estimates?*

Our project called for hosting the ACRL day-long workshop, “Scholarly Communication: From Understanding to Engagement” in the fall and survey the library staff who do scholarly communication tasks in order to create a network, share best practices, and look for opportunities to collaborate on projects. We hosted the workshop on 9/30/2016, with 45 attendees. The next step will be to create the survey. We are currently right on track.

2)            How is spending progressing when compared with the original budget estimates? (You may also choose to detail issues regarding access to funds in the next three questions).*

We applied for $20,000 grant but only received $10,000. We have spent approximately $8200 of that amount on the conference.

3)            Please provide feedback regarding your experience with the project execution, in particular any issues or roadblocks you’ve encountered that may have been unexpected.*

It will be challenging to complete all the tasks we set out to do with only half the funding.

4)            What are your positive observations or pleasant surprises about your team’s interaction or project process that might would be helpful to other PI’s?*

Initial feedback from conference attendees include such comments as:

“these conversations refresh my enthusiasm for scholarly communications issues”

“I want to get our faculty up to speed and comfy with OA but my info dates back to 2006; I need(ed) a refresh”

“(I am) meeting others in my field, gaining new knowledge, learning new ways to help faculty and students”

“I feel less alone in this SCHOLCOMM world”

5)            Please describe any challenges you’ve encountered working with your project team that you’ve found solutions for that might be helpful to other PI’s.*

NYLA Scholarly Communications Unconference

Recap of the Scholarly Communication Unconference held at NYLA, 11/2/2016

1.    Peter D. Barvoets, SUNY Cobleskill
What I learned in getting almost 100 students to publish their presentations from the SUNY Undergraduate Research Conference (SURC 2016)

Main takeaway – sent email permissions 5 days before event, was at conference with laptop to capture presentations as students registered.

2.    Amy Schuler, Cary Institute of Ecosystem Studies
Providing research data management training for students
Main takeaway – summer research institute for undergraduates. Teaches data management. Great presentation.

3.    Jeremiah Hall, Bard College
Digital Commons Platform for a Small College IR
Main takeaway – Instructional resources, Oral Histories, Senior Projects

4.    Kim Myers, The College at Brockport
Starting a library publishing program http://digitalcommons.brockport.edu/lib_presentations/14/

5.    Pamela McLaughlin, Syracuse University Libraries
Sound Beat: an innovative media publishing initiative at Syracuse University Libraries
Main takeaway – 2 minute sound bites on a variety of subjects, musical and otherwise. Librarians work with one or two classes a semester to produce these. Posted on a Wordpress site, use only clips so it is used as transformative, avoid copyright police.

6.    Alice Carli, Sibley Music Library, Eastman School of Music, University of Rochester
A digitization project leading to publishing a large number of texts (including musical scores, in our instance) on our digital repository
Main takeaway – Multiyear project to digitize and conserve fragile scores in the SML. Those in public domain made public in the U of R’s IR+, those still in copyright put up with embargos, and made public only to U of R community.

7.    Jiebei Luo, Skidmore College
1. Creating an auto embargo reminder by utilizing Google Gadgets (Google form, Google Spreadsheet, formMule add-on script, Google calendar). 2. Building a live statistic Google site (iFrame, Google)
No takeaway here. Sophisticated use of Google Apps, but what doesn’t make sense is WHY? Why create work outside the IR (Digital Commons), when it is already provided?

Main conference takeaway –The above lightning rounds took place in the morning. The afternoon was devoted to a World Café, where the audience determined the topics. Of all the possible topics to discuss at this unconference, how to start and run an IR, engage with faculty, etc. was what most people wanted to talk about. Brockport is way ahead of the game there.

Links to presentations: https://drive.google.com/drive/folders/0B5BZ7sQZ7CRUa3RqWWdabllYems

Live linking an event for an event community

Problem: When you want to refer to a Related Website in an event community, the link works on the Schedule page. It doesn't work on the related metadata page, however.

Example: http://digitalcommons.brockport.edu/dcglug/ 
Ask the Experts event works fine on the schedule - it takes you to: https://padlet.com/kmyers20/pfq43sp4oegj, but on the actual metadata page, it does not. 

Solution: Bepress can add a WYSIWYG field - here are instructions from Lauren:
I’ve made the change for you. Take a look at the submission form:
http://digitalcommons.brockport.edu/cgi/ir_submit.cgi?context=divconf&edbypass=1
You’ll see there is now two “Event Website” fields. The first one is the one that was already there. I’ve added some instructions- “Enter the URL that should display on the schedule page. Do not use HTML.” This field will pull the URL straight onto the track:
http://digitalcommons.brockport.edu/divconf/2016/
The new field also called “Event Website,” is a WYSIWYG field. The instructions read “Enter the URL that should display on the article information page. Use the WYSIWYG field to link the URL.” You should enter the same URL, then use the little chain icon to link it. This field will pull the URL into the article information page, here:
http://digitalcommons.brockport.edu/divconf/2016/schedule/21/ Because you’ve used the link feature, the item will be hot linked, as you requested.

Ta-da!

Diversity and other conferences - making the schedule appear main page

For years now I thought that Support had to work the magic that made the schedule appear on the front page of an event community. Nope, it turns out it is as simple as embedding the Introductory Text on the schedule track page (duh). Of course, then you have to run both a tract level (schedule) and a theme level (year) update to get it to show up.

From the correspondence files:
I think what we’ve got here is another case of the introductory text in the theme configurations instead of the track configurations. If you look at the configurations for the track from 2015, you’ll see that it’s <h3>:
http://digitalcommons.brockport.edu/cgi/user_config.cgi?context=divconf/2015/schedule
The track level for 2016 is still showing the h2:
http://digitalcommons.brockport.edu/cgi/user_config.cgi?context=divconf/2016/schedule
You’ll want to update the track level configurations to match that <h3>, then run a track level update and a theme level update.

I might also suggest removing the theme level (2016) introductory text from this year (and maybe 2015) so you don’t run into this again next year.

Another new discovery - if you want to keep text in the coding, but hide it from view the way to do that is - <!-- text to be hidden -->.

Digital Commons User Group planning

6/14/2016: Met with Monica Dailey from C & E, and Jules over at LAB to look at our space needs. We decided on the McCue Auditorium for most of the day, with the workshop to be held in Rm206A/B, lunch on the second floor lounge and English conference room, and breaks on the first floor.

I filled out the Visitor Parking Pass request and spoke to Dave in Parking, and will drop that off today. Parking will be requested in the T lot - no charge.

I updated the online schedule with room assignments (though the DC website appears to be down at the moment).

I will meet with library colleagues today to plan a Thursday night event - ideas include:
Wine & Cheese reception (maybe without the wine)
Tour of the library and archives
Dine Arounds
Tour of downtown
Pick up registration packets

Talked to Patty Sorel (2379), confirmed our arrangements for the User Group meeting, and our reservation for the NY Room for 9/30. (6/21/2016)

Talked to Susan Vasquez, building coordinator for LAB about air conditioning and use of TV. She referred me to Facilities (2408) for the HVAC, and said the process for using the monitors is to get them approved by the building (deans, etc.) and then it goes to Kurt for uploading. They would need to be pdf. Very cool! I can send her a sample of the slideshow next week for approval, and then the final product can go directly to Kurt. (6/22/2016)