Draft protocol for serving BagIt repositories RESTfully
edsu/dflat 19
an implementation of the dflat and redd specifications from CDL for versioning of digital objects
Vanilla-plus Hyrax app for testing and tire-kicking
A basic implemention of Archival Resource Key utils in Python
example app for looking at data in elasticsearch based on a crawl of a site with microdata
A webextension for Firefox. Pretty-prints JSON content in the browser for easy, unobtrusive viewing.
Import delicious bookmarks into Google Bookmarks
an implementation of the dflat specification for digital preservation filesystems
created tagsul-dlss/dlme
Digital Library of the Middle East web application, based on Spotlight
created time in 2 days
push eventsul-dlss/dlme
commit sha 0ff250e589aae78894f02af356be6e3d408c26cc
Update Ruby dependencies
commit sha 4bfc16c7c049a5e5a4ebc377c98e840ec38d6e4d
Update Yarn dependencies
commit sha 4e188b4f51c6c99b7f9a38c71276a90216c3b816
Merge pull request #1298 from sul-dlss/update-dependencies
push time in 2 days
push eventsul-dlss-labs/iiif-app-example
commit sha 8a6d542cc0f75c73e37f8b24b87498b9c7fd6839
Update the manifest url to the corrected dime novel
commit sha 1199018a1bfd0cfbda7ce8e4000bcac3e1d2e459
Merge pull request #8 from sul-dlss-labs/corrected
push time in 5 days
PR merged sul-dlss/sul-requests
This PR extracts some non-location information out of the LibraryLocation class, where additional behaviors seem to have accumulated over the years. Before starting to apply re-opening rules, it seemed like a good opportunity to clarify some of these components.
There are 3 major changes:
- extracting some of the business logic into YAML configuration
- extracting the
LocationRulesandRequestAbilityclasses to evaluate what types of requests can be made for a given library/location/item_type/etc - cleaning up some loose ends in order to re-focus
LibraryLocationon location-specific data accessors.
For slightly easier reviewability, I've left the original tests for the different types of requests intact (with a little mechanical transformation to use consistent naming, etc). Possible follow-up would be to move some/all of those tests onto LocationRules/RequestAbility.
pr closed time in 6 days
push eventsul-dlss/sul-requests
commit sha 9121c5affb31408bbab1aa944573c035e8e4744c
Pull mhld accessor over to Holdings concern
commit sha f7d43643fe67922af0b4dc49ca1e60f3c59a564e
Extract business logic specifications for request types into YAML
commit sha 6629af70c56180a8078572d52e4826f0be818711
Extract -able? checks for what type of request can be made into a new class
commit sha 5f909666f9633a8fbba81b17295349d91e92d50f
Stop passing the whole request to LibraryLocation
commit sha 616ca758fe2c7d31daff85db3feb72603c70bb0b
Merge pull request #1191 from sul-dlss/settings-data
push time in 6 days
push eventsul-dlss/exhibits
commit sha 9a975360085afc6b777c6abff8641af0e848986e
Skip custom thumbnail generation for thumbless uploads; fixes #2107
commit sha 958b106fec514542fc5c2a0bab57c6bee7b99695
Merge pull request #2115 from sul-dlss/2106-thumbless-upload Skip custom thumbnail generation for thumbless uploads; fixes #2107
push time in 8 days
issue closedsul-dlss/exhibits
Backtrace
line 40 of [PROJECT_ROOT]/config/initializers/spotlight_initializer.rb: block (2 levels) in <main>
closed time in 8 days
cbeer
issue closedsul-dlss/exhibits
Adding new items to Opening Night! are not saving and reindexing results in an error
Submitted by exhibit curator Ray Heigemeir on 8 July 2021:
After a period of hibernation, we want to begin adding new entries to the Opening Night! database. We added two yesterday, but they don't appear to have "saved." The titles were "Guru" and "Happiness is the problem." I reindexed and the blue "reindexing" indicator seems to still be incomplete (after three hours). Not sure where the problem lies.
Could someone investigate when time allows?
closed time in 8 days
caaster
issue commentsul-dlss/happy-heron
Record terms of deposit acceptance in database
@mjgiarlo That's right. Though to clarify, you should see the box there, but it would be checked.
Ah yes, thank you!
Once a year is the time we have currently in Hydrus I think and that works fine, so I'd say go with that.
That sounds reasonable to me, too.
Thanks, @mjgiarlo. Didn't mean to pull you away from other things!
np!
comment created time in 9 days
issue commentsul-dlss/happy-heron
Record terms of deposit acceptance in database
As I understood it, this issue is about changing ToD acceptance from a work- (or work version-) specific implementation to a user-specific implementation.
comment created time in 9 days
PR opened sul-dlss/mise
Connect to #167
This is a work-in-progress commit, as I have now unassigned from #167. Feel free to use this or ignore it or dump it.
pr created time in 16 days
issue commentsul-dlss/mise
Remove "exit workspace" part of the Save workspace button action
Unassigning for now as I'm focused on hiring atm.
comment created time in 16 days
push eventsul-dlss/course_reserves
commit sha 1cab62028334fb505b4d6cf4b2fe17409d0d76bd
Add additional legacy reserve properties
commit sha 2d7b69b6de841f0e6c0dbefd5a7292861efd622a
Merge pull request #338 from sul-dlss/resv-props Add additional legacy reserve properties
push time in 20 days
issue closedsul-dlss/course_reserves
Backtrace
line 2 of [PROJECT_ROOT]/app/views/reserves/_reserves_item.html.erb: new
line 2 of [PROJECT_ROOT]/app/views/reserves/_reserves_item.html.erb: _app_views_reserves__reserves_item_html_erb___3526101875076988257_29360
line 95 of [PROJECT_ROOT]/app/views/reserves/_reserves_form.html.erb: block in _app_views_reserves__reserves_form_html_erb__3300027265855129073_29300
closed time in 20 days
cbeer