mjgiarlo

counts = Hash.new([])

Dir.glob('*/.rubocop.yml').each do |file|
  YAML.load_file(file).tap do |cops|
    cops
      .select { |k, v| v.is_a?(Hash) && v.key?('Enabled') && !v['Enabled'] }
      .each { |key| counts[key.first] += [file.split('/').first] }
  end
end

mjgiarlo

// Forked from https://gist.githubusercontent.com/camillevilla/16b53c50eccc11de0cb40ee0be7dcf03/raw/51f2473d5b04bb72e835ac9168381d87c0961d31/github-pr-urls.js

// PR search at https://github.com/pulls
// is:pr org:sul-dlss head:update-dependencies created:2018-05-08..2018-05-09

// Repo order used in our update script and status table
// https://github.com/sul-dlss/access-update-scripts/blob/master/infrastructure/ruby
var repoList= "argo common-accessioning dlme dlme-harvest dlme-transform dor-services-app dor_indexing_app dor-fetcher-service gis-robot-suite google-books hydra_etd hydrus lyberservices-scripts modsulator-app-rails preservation_catalog preservation_robots pre-assembly repository-api rialto-etl rialto-webapp robot-console sul_pub sdr-services-app was-registrar-app was_robot_suite was-thumbnail-service workflow-server-rails"
repoList = repoList.split(' ')

mjgiarlo

ActiveRecord::Schema.define(version: 20_171_026_154_256) do
  create_table 'resource_stats', id: :serial, force: :cascade do |t|
    t.datetime 'date'
    t.integer 'hits'
    t.string 'hit_type'
    t.string 'resource_id'
    t.string 'resource_type'
    t.datetime 'created_at', null: false
    t.datetime 'updated_at', null: false
    t.integer 'user_id'

mjgiarlo

InvertedHashOperator.new <= 'hash_key'
=> {"hash_key"=>#<InvertedHashOperator:0x00000002d67a20>}

mjgiarlo

diff --git a/Rakefile b/Rakefile
old mode 100644
new mode 100755
index a0ec74f..e5f6985
--- a/Rakefile
+++ b/Rakefile
@@ -9,22 +9,16 @@ Sulbib::Application.load_tasks
 task default: [:ci]
 
 desc 'Continuous integration task run on travis'

mjgiarlo

Here are the divergences I found with https://github.com/projecthydra/sufia/wiki/Understanding-Admin-Sets-Participants

Admin Set Managers

1. Admin Set managers can not currently edit Admin Set metadata until they are elevated to repository administrators. This is because only repository administrators can access the Admin Set edit UI, which is under /admin/. When an Admin Set manager deposits to an Admin Set, they have edit access.
2. Admin Set managers can not edit works simply by virtue of being Admin Set managers; this is controlled by the work's ACLs still.

These two are yet-to-be-implemented features.

Admin Set Depositors

mjgiarlo

$ rspec spec/controllers/collections_controller_spec.rb:224
Run options: include {:locations=>{"./spec/controllers/collections_controller_spec.rb"=>[224]}}

Randomized with seed 3418

CollectionsController
  #delete
    when it succeeds

[20, 29] in /home/mjg/workspace/sufia/app/controllers/concerns/sufia/collections_controller_behavior.rb

mjgiarlo

11c605d Pass url options to SearchState so collection route can be resolved
3a54041 Adding link to referenced work in all workflow notifications
9115d6b Change copyright in the footer to 2017
6ad2760 Move url_for_document to SearchState
18e3a1f Use the new db-backed minter from AF::Noid by default.
2a5aab5 Adding a link to the work into the notification message
4b53b01 Travis should test with the latest Rails (5.0.1), since bundler is already picking it up
0018701 Replace references to CurationConcerns. Fixes #29
b61811f Move WorkflowActionsController to the Hyrax namespace
9ac3d28 Restore WorkflowActionsController

mjgiarlo

{
  "workflows": [
    {
      "name": "one_step_mediated_deposit",
      "label": "One-step mediated deposit workflow",
      "description": "A single-step workflow for mediated deposit",
      "actions": [
         {
           "name": "deposit",
           "from_states": [],

mjgiarlo

    sufia was resolved to 7.0.0.beta1, which depends on
      curation_concerns (~> 0.14.0) was resolved to 0.14.0, which depends on
        hydra-head (~> 9.9) was resolved to 9.9.0, which depends on
          hydra-core (= 9.9.0) was resolved to 9.9.0, which depends on
            hydra-access-controls (= 9.9.0) was resolved to 9.9.0, which depends on
              active-fedora (~> 9.10.0)