#lpf24 — Public Fediverse posts

ICYMI: Last week, IOI's Lauren Collister gave a talk on #InfraFinder at #LPF24! You can see her slides at the link below.
https://docs.google.com/presentation/d/1kwCQL_LncpBv3l1Fvhv_H8YYqQOdvrAAts-x9pf1wJQ/edit?usp=sharing

ICYMI: Last week, IOI's Lauren Collister gave a talk on #InfraFinder at #LPF24! You can see her slides at the link below.
https://docs.google.com/presentation/d/1kwCQL_LncpBv3l1Fvhv_H8YYqQOdvrAAts-x9pf1wJQ/edit?usp=sharing

To sum up my remarks at the close of the final #LPF24 session:

As library people we have no business asking for things and doing things that do not comport with our values as librarians. when we abandon who we are, we abandon what makes working in libraries important and special. so don't do bad stuff. only do good stuff.

blog post forthcoming next week.

apropos: I need to observe how fortunate those of us who work here are to be at this university with the amazing resources we have available to us. not everywhere is as well resourced as we are. we have an embarrassment of riches.

and not just in women's hockey.

#LPF24 #ThisIsGopherHockey #GWH

#LPF24 attendees enjoying our #UMNProud PAWS (Pet Away Worry and Stress) therapy dog, Ranger (with human friend Mark).

Very fortunate to have them visit my library every two weeks.

#LPF24: talking about the research agenda for Library Publishing!

#LPF24

I am happy to talk to people about alternatives to GAnalytics which we use here at U. Minnesota.

#UMNProud

Slides for our "Equitable Access" presentation at 10. #LPF24 #LPForum24 https://docs.google.com/presentation/d/1o5Z3Q0YbmtKLAGSGzJawBSEIB9nrh21F1M7nn1a9arE/edit?usp=sharing

Slides for our "Equitable Access" presentation at 10. #LPF24 #LPForum24 https://docs.google.com/presentation/d/1o5Z3Q0YbmtKLAGSGzJawBSEIB9nrh21F1M7nn1a9arE/edit?usp=sharing

@investinopen @lbcollister Thanks for the info!
I'm tagging this with #LPF24 so other folks can find it as well

@platypus also, I'm at #LPF24 with your distinguished colleague Ally L.

In a panel on Diamond #OpenAccess at #LPF24, not only did a speaker recommend the COKI Open Access Dashboard, but they also mentioned some of its data sources, including @crossref and ROR. Read our discussion with @cameronneylon of COKI at https://ror.org/blog/2024-01-17-coki-case-study/

In a panel on Diamond #OpenAccess at #LPF24, not only did a speaker recommend the COKI Open Access Dashboard, but they also mentioned some of its data sources, including @crossref and ROR. Read our discussion with @cameronneylon of COKI at https://ror.org/blog/2024-01-17-coki-case-study/

turns out people aren't always careful with creating metadata and this kinda fucks up automating a huge number of IR uploads (oops) #LPF24

#LPF24 Automating institutional repository uploads. Heavens to Murgatroyd I know where this is heading.

#LPF24 I like this Jason Boczar person.

could someone please tell Jason to speak up? my gesticulating from the back isn't working.

#LPF24

"an open source platform" (that requires enormous computing power and resources out of reach of smaller universities so please pay our vendor of choice.)

#LPF24

University presses share the same values as libraries? Really? REALLY? news to me.

#LPF24

BTAA schools share library collections to the extent that together we're the 3rd largest library in the world.

#LPF24

#LPF24: talking about the #B1G "Ten" Academic Alliance (BTAA)

I make no comment with no disrespect intended to our new "family" members at Washington, Oregon, UCLA, and USC.

I have no comment about the destruction of a 100+ year old athletic and academic alliance because of TV Revenue, nor do I have any thoughts whatsoever about the fact that they're soon going to be flying teams across the GD country to play a single basketball game. No comment.

I think it's just great. We're a family. hooray for us!

#LPF24: and here we are with my friend and former colleague Stephanie Westcott and former fellow Virginian Jessica Kirschner talking about the awesome work they're doing at #VIVALib building a statewide #OER publishing program over in Virginia.

#LPF24: "Everyone has a price" what a way to end a panel.

#LPF24: for anyone looking for the lardbucket site that Shane N. just mentioned:

https://2012books.lardbucket.org/

#LPF24: as an aside one person in a panel that will remain unmentioned alludes to rapidly increasing pressbooks (vendor run hosting) costs.

Pressbooks, for context, is at its core an open-source wordpress plugin. It is not hard to manage. TBQH it is very easy to manage.

I wonder if we could potentially do something about that HMMMM.

CLEARS THROAT VERY AWKWARDLY

HMMMM.

Just realized that the #LPF24 session I am attending was actually a set of two presentations and now I am stuck hearing a talk about how useful ChatGPT can be, so... that's awkward

#LPF24: I deeply resent needing to create a discord for this conference when I (and no doubt the majority of people here) already have slack (for all its faults)

ROR is at the Library Publishing Forum today, the annual meeting of the Library Publishing Coalition. We’re starting the day with a keynote from Katherine Skinner of @investinopen #LPF24

ROR is at the Library Publishing Forum today, the annual meeting of the Library Publishing Coalition. We’re starting the day with a keynote from Katherine Skinner of @investinopen #LPF24

#LPF24: hold on gotta make this really awkward

Open infrastructures can advance open values, are customizable, & can be adapted as needs grow. But their adoption trails behind their competitors." ~Katherine Skinner #LPF24

Open infrastructures can advance open values, are customizable, & can be adapted as needs grow. But their adoption trails behind their competitors." ~Katherine Skinner #LPF24

#LPF24: taking a minute to go stare at the vendors selling ostensibly opensource code monsters. Or closed source garbage (and I have friends who work at one of those places!).

BRB gotta do this really quick and really awkwardly.

#LPF24: (similar to what I said last night, tbqh: https://tilde.zone/@anelki/112442751016398118)

Put money where our values are honored!

1. open source
2. open access
3. can be managed by libraries themselves, not dependent on vendors.

#LPF24: (similar to what I said last night, tbqh: https://tilde.zone/@anelki/112442751016398118)

Put money where our values are honored!

1. open source
2. open access
3. can be managed by libraries themselves, not dependent on vendors.

#LPF24: this only happens because we operate on our values! and as long as we remain true to our ethics as librarians, we will keep making progress!

#LPF24: this only happens because we operate on our values! and as long as we remain true to our ethics as librarians, we will keep making progress!

#LPF24: partnerships are critical and this community has 10 years of success in that regard! Strategic partnerships like with @PublicKnowledgeProject are really critical!

#LPF24: we are a movement. this is the 10th annual Library Publishing Forum and we have built a community that is engaged, curious and thoughtful community.

we also have 10 years of documentation shared between institutions that builds us up together.

all of this made possible by library members providing the leadership we need.

#LPF24: we are a movement. this is the 10th annual Library Publishing Forum and we have built a community that is engaged, curious and thoughtful community.

we also have 10 years of documentation shared between institutions that builds us up together.

all of this made possible by library members providing the leadership we need.

#LPF24: why did this work?

1. We tried to do it and put everything into it.

2. Universities committed to actually doing it

3. we had a well considered plan to do it: conferences, creating a directory of programs, sharing documentation and policies

4. it was completely community driven and organized. Educopia/LPC were only facilitating the things that needed facilitating as determined by the members.

5. the people involved were absolutely committed to doing it and doing it well.

#LPF24: why did this work?

1. We tried to do it and put everything into it.

2. Universities committed to actually doing it

3. we had a well considered plan to do it: conferences, creating a directory of programs, sharing documentation and policies

4. it was completely community driven and organized. Educopia/LPC were only facilitating the things that needed facilitating as determined by the members.

5. the people involved were absolutely committed to doing it and doing it well.

#LPF24: the point wasn't to create a new non-profit, the point was to get a community driven initiative going.

this started on a shoestring, not with a huge budget, not funded by major foundations. Just the libraries that were contributing themselves.

#LPF24: the point wasn't to create a new non-profit, the point was to get a community driven initiative going.

this started on a shoestring, not with a huge budget, not funded by major foundations. Just the libraries that were contributing themselves.

#LPF24: 2012 Katherine Skinner, Charles Wilkinson, et al., began defining what library publishing is:

1. Subsidized Production to support free and open access.

2. Digital First: we cannot be burdened by the need to make printed copies of everything.

3. Metadata and information management over marketing and sales. Make your stuff discoverable. Don't worry about sales.

#LPF24: early 2000s, you couldn't call it Library Publishing. It was considered too problematic. But that's what Emory was doing.

up now: Katherine Skinner from @investinopen giving the keynote: a history of the open-publishing and library publishing movement.

#LPF24

#LPF24 Observation: the number of people wearing masks (easily > 2/3rds) is really nice and also there's improved air filtration in the session rooms. Great job LPC and LPF Program Committee!

really I should just make a GD blogpost about this...and I will but also I am doing laundry and am exhausted.

#LPF24 #PKPSprint

I will say, and I'm sure this will come up at #LPF24 tomorrow and Thursday:

for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.

To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.

The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?

The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?

Compare this to something like @PublicKnowledgeProject's Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible.

Not based on the popular programming language of the week. Not based on whatever the latest trend is.

Built on technology that very simply: JUST WORKS.

...and yes, we can make it have a slide carousel on the front page.

*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack

#PKPSprint #LPF24 #C4L24

also as I just noted IRL:

THANK YOU to the @PublicKnowledgeProject folks for developing platforms and software that aren't, for lack of a better and more succinct expression, a roaring tire fire.

imagine that.

#LPF24 #PKPSprint

All I'm saying is don't reinvent the wheel every other week and don't over-complicate things.

PLEASE I am begging you people.

#LPF24 #PKPSprint

Specifically thinking of systems that I have openly criticized before, including one developed/funded by a different unit at my own university which I actively disdain.*

5 MB pages for...text....because you're loading in 20 webfonts from multiple CDNs. Using 2-3 GB of RAM on a brand new VPS and a brand new install because you've got an enormous Rails application doing nothing but sitting there with no users or publications. That's not kosher. Don't abuse users like that. Especially students from disadvantaged backgrounds or people with lower-bandwidth internet connections.

see also: node apps that do the same thing.
see also: rust web assembly apps that do the same thing

what if instead we use lightweight, easy to use, and accessible applications driven by cross-platform Apache/PHP/MariaDB/etc.??

Not shiny. Not sexy. It just works. and works well, tbqh.

*manifold. it's manifold.

#LPF24 #PKPSprint

today (now that I'm in the pre-conf after some administrative stuff): talking about @PublicKnowledgeProject's role in the #OpenPublishing #ScholComm #OpenAccess ecosystem (hint: it's really gd important) (2nd hint: and immensely better than the alternative)

#PKPSprint #LPF24

okay so things are ✨happening ✨!!

1. Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.

2. Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.

3. Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.

4. Porting in further language/translation and accessibility improvements, especially for plugins

5. Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.

6. More documentation: integrating progress from previous sprints including for newly created plugins.

7. (Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)

@PublicKnowledgeProject

#PKPSprint #LPF24 #a11y

Reblog via anelki

at the request of some UMN editors, I’ll be exploring ways to potentially integrate activity pub into PKP publishing projects.

@PublicKnowledgeProject

#PKPSprint #LPF24 #UMNProud

what are we even doing here??

but lets see how this works, ie., wordpress creating activitypub posts. Could we use this for PKP/OJS? how would that work?

#LPF24 #PKPSprint

https://wp.anelki.net/2024/05/13/wordpress-as-an-activitypub-actor-could-we-use-this-for-pkp-ojs/

#LPF24 #PKPSprint

Hello JATS XML, my old frenemy.

#PKPSprint #LPF24

how can we collaborate and scale up our work making OJS/ @PublicKnowledgeProject more accessible? Instead of retreading what others are doing locally in our own instances.

Ideas are happening.

#LPF24 #PKPSprint

PHP Warning: require_once(lib/pkp/lib/vendor/autoload.php): Failed to open stream: No such file or directory in /var/www/ojs/lib/pkp/includes/bootstrap.php

it's right there wtf are we doing here php!!??

#PKPSprint #LPF24

at the request of some UMN editors, I'll be exploring ways to potentially integrate activity pub into PKP publishing projects.

@PublicKnowledgeProject

#PKPSprint #LPF24 #UMNProud