Versions Compared

Old Version 4

changes.mady.by.user Valorie Hollister

Saved on

compared with

New Version 5

changes.mady.by.user Valorie Hollister

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. News
    1. Welcome 2 new DCAT members!
      1. Maureen Walsh, The Ohio State University
      2. Amy Lana, University of Missouri
    2. Remaining 2011 DCAT meeting dates:
      1. October 11, 2011
      2. November 8, 2011
      3. December 13, 2011
    3. DSpace 1.8 - 1.8.0 Release Notes
      1. 1.8 features are frozen
        1. DCAT features in 1.8:
          1. half of DS-638 Enable virus checking during submission
          2. DS-749 Reordering of bitstreams
        2. DCAT features that didn't make it
          1. DS587 tombstone
          2. DS638 check file format
        3. Apple U codeiTunes podcast Apple U DS-528 RSS feeds
        4. Complete list of features
      2. testathon this wk (end 9/23)
      3. final release still targeted for mid-Oct
    4. DuraSpace 2011 Sponsorship Campaign: $285.5k with 50 sponsors so far, 16 of which are new for 2011, blog post update
    5. New DSpace Committers - Kevin Van Develde from @mire
    6. OR12 DSpace User Group Meeting Chair: Robin Rice, University of Edinburgh/EDINA
    7. Other news?
      1. anyone attend the EIFL online workshop Sept 9?
      2. anyone attend Readiness for REF (R4R) Workshop on Sept 5 in London?
      3. Dublin Core 2011, The Hague, Sept 21-23: Bram planning to put together informal DSpace user mtg together
  2. Update on DCAT Review
    1. Committer requested help
      1. Revised/updated metadata schema - committers have requested our input on what we want out of the box
        1. Bram has developed a survey
          1. Phase 1 - DCAT members will all respond to the survey and have discussion on email list - responses until Aug 26
          2. Phase 2 - community-wide survey, results from DCAT survey will help focus the public survey, Val and Bram to get into Surveymonkey by Aug 31
          3. Feedback Leonie Hayes on this
          4. Dublin Core Challenges for DSpace
        2. current Surveymonkey versionhttps://spreadsheets.google.com/spreadsheet/viewform?formkey=dDFhNUI5TjZBdEtsU3NJTHplV1NMb1E6MQ
          1. sent to committers for feedback
          2. send out to community before the end of September
      2. DS-811 delete/withdraw items via bulk csv editing
        1. feedback requested from Stuart:
          1. DCAT members present liked the idea and thought it would be a helpful addition to the Bulk Metadata Editing feature -- which soon will need a new name, since it's no longer just "metadata editing"
          2. A few were concerned about deleting objects via the CSV file accidentally by writing the word 'delete' in the wrong row and since the delete is permanent it could very detrimental - others liked the power to delete things in bulk. To address this a few members suggested that the bulk deletion would be able to be turned on/off (based on local policies and needs) in the config. Withdraw, on the other hand, could always remain on, since you can easily undo withdrawa by reinstating the object.
          3. There was some additional discussion on terminology -- using 'expunge' vs. 'delete' -- which may help prevent deletion errors. DCAT members also liked that by using 'expunge' it would be consistent with the rest of DSpace and sounds more permanent than 'delete'. Further research indicates that DSpace current references the following --> which shows some current inconsistency/both terms used interchangeably:
            1. Wiki Markup
              XMLUI Edit Item: "Completely expunge item: \[Permanently Delete\]"
            2. JSPUI Edit Item: "Delete (Expunge)"
          4. A few members thought more status msgs would also be a good improvement -- these msgs would be generated once the upload operation is completed -- reporting feedback on what was completed -- something like "X rows uploaded,  X changes completed" or "no changes were detected". Not sure how challenging this would be -- but everyone seemed to agree that marking "withdraw" on a withdrawn item should do nothing, but that it should report that "no changes were detected" if possible.
          5. Please add other comments to JIRA DS-811!
    2. Update on previously reviewed items (items * were the ones discussed during the mtg)
      1. *DS587 tombstone (Sarah):discussion forum,JIRA
        1. Jose Blanco has submitted patch for both JSPUI and XMLUI
        2. Richard Rodgers is reviewing and tweaking the patch, hoping to have it completed by Fridaywas to review and tweak the patch
        3. did not make it into 1.8
      2. *DS638 virus checking/check file format /virus check (Elin):discussion forum,JIRA
        1. virus checking is complete and code has been committedin 1.8
        2. file format checking is written and tested, unclear about whether or not it will make it in w/other Curation Task work being done by MIT, more discussion to be had at the Developer Mtg on 8/17but did not make it into 1.8
      3. *DS749 allow for bitstream order to be changed (Jennifer):discussion forum, JIRA
        1. in 1.8
      4. DS164 deposit interface for modifying input forms.xml (Jim): discussion forum, JIRA https://jira.duraspace.org/browse/DS-164
        1. GSoC project - do away with item-submission.xml and input-forms.xml and instead create an Admin UI that allows repo managers reorganize the submission UI
        2. GSoC student wants to continue work on project
        3. Jim and other DCAT members provided specfic requirements list to GSofC list and on sample screenshot wiki page
      5. DS-560 XMLUI News in config dir (Bram): discussion forum, JIRA
        1. XMLUI interface is not as useful as JSPUI for news config, Bram proposed to have a more flexible front page
        2. Bram to re-send discussion link - all DCAT members to chime in on broadened scope (not just XMLUI, not just news) to come up with a general consensus of the types of optional configurable elements that the community would like to see and/or the functional req'mts (news box, statistics, list of comm/coll, what ever front page needs)
        3. After Do we have a DCAT consensus, we will ? If so, does it still make sense to hold a community-wide discussion for both feedback and developer resource identification?
      6. DS-456 create easy upgrade scripts (Iryna): discussion forum, JIRA
        1. no developer assigned yet
        2. propose writing scripts for the most common database/operating sys
        3. Database: PostgreSQL 264, MySQL 43, Oracle 39, Other 6
        4. Operating Sys: Linux 224, Microsoft Windows 88, UNIX 28, Solaris 22, HPUX 2
        5. Michael to attach scripts to JIRA issue that they have developed
        6. hold community-wide discussion/solicitation of other upgrade scripts already written or interested parties
  3. Meeting Attendees:

...