Versions Compared

Old Version 7

changes.mady.by.user Mark Custer

Saved on

compared with

New Version Current

changes.mady.by.user Mark Custer

Saved on

Key

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

...

  • Next round of development with HM (set up a proper JIRA sprint?)...  https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=3&projectKey=AR&view=planning.nodetail&quickFilter=11 
    • Plugin-ification of the pui-new, 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1628
    • Update solr indexer as needed to ensure that:
      • users can search with and without diacritics (e.g. enabling the ISOLatin1AccentFilterFactory); search for "Lemaitre" should still return a record with "Lemaître" in it). 
        Jira Legacy
        serverJIRA (archivesspace.atlassian.net)
        serverId36c489e2-4fb0-353a-985b-64038401be2f
        keyAR-1629
      • the index is as light-weight as possible for the PUI (see, for instance,
        Jira Legacy
        serverJIRA (archivesspace.atlassian.net)
        serverId36c489e2-4fb0-353a-985b-64038401be2f
        keyAR-1300
        )
      • everything is available in the index that needs to be there for display purposes.  at this point, I could only identify the following two things missing for display purposes:
        • related accession/resource titles to meet requirements for Cherry Hill designs
        • related agent record names for classification/subclassification pages to meet requirements for Cherry Hill designs.
      • highlighting of search terms if possible (and displaying keywords in context even if a stemmer is employed locally); 
        Jira Legacy
        serverJIRA (archivesspace.atlassian.net)
        serverId36c489e2-4fb0-353a-985b-64038401be2f
        keyAR-1489
         and
        Jira Legacy
        serverJIRA (archivesspace.atlassian.net)
        serverId36c489e2-4fb0-353a-985b-64038401be2f
        keyAR-1490
         are related, but do we want to create a separate ticket for this?
    • Single-scroll view of an entire resource record (i.e. the ability to review a resource record and all of its descendants, in chunks / minus inherited info, without having to go to a separate web page for each resource component.  See the very-large http://archives.nypl.org/mss/2233#detailed as an example.  If we follow this example (i.e. adding a navigation panel for series/subseries or record group/subgroup levels that only load those sections at a time), I think that would make a lot of sense; however, we also need to have a single-page view even if series/subseries and/or recourd group/subgroup levels aren't included in a finding aid.  See also NCSU example: https://github.com/NCSU-Libraries/aspace_public 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-838
       (should we separate this into it's own ticket since the original request bundled the options to view the finding aid in intellectual order and physical order?)
    • Finish up the Classification / Record Group views (at the very least, add the same functionality that’s available in the current PUI, and then adding a Classifications accordion to any record associated with a classification, as already implemented in Brian’s code). 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1630
       and 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1063
    • Finish up linked accessions / resources work in the new PUI as per the Cherry Hill design (currently missing is the accordion section on a resource page with linked accessions, along with the accession type, title, dates, and identifier). We also need conditional logic to determine a) what displays in the accordion (i.e. only linked accessions that are published should display) and b) what shows up in the “unprocessed material” section as a stand-alone webpage (i.e. only published accessions that do not have a processing status set to “complete” OR that do not have a processed event record that’s set to “pass” should show up as an unprocessed collection in the PUI / in the PUI solr index) 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1481
       (also not illustrated in the CH designs are related resources on an accession landing page).
    • Ensure that an unpublished Repository and its resources/accessions/etc. do not display in the new PUI.  Currently, an unpublished Repository still has a value of published = True in the staff interface (e.g. see AARome at http://aspace.hudmol.com:7300/repositories): 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1546
    • Add the PDF request feature (preferred method: enable some ability to create the PDF file dynamically and provide it to the researcher, probably via a temporary link due to potentially large file sizes; alternative method 1: enable a configuration so that a link to another webserver or Git repo can be provided; alternative method 2: update Mark Cooper’s plugin to work with the new PUI, with the usual caveats that this won’t work for large finding aids). 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1471
    • Add a mailer to finish out the requirements for the Request feature, which will generate an email with the information outlined in
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1064
      .  Mark Cooper also suggested sending the requests to the ASpace staff UI, which makes a lot of sense, but that would require a lot more staff-side development, and it would also push ASpace in the direction of AT Reference.  Hopefully an email will suffice for now.  Will also need a configuration option to turn off the "Request" button altogether if that's not already available (other configuration options exist for the request feature, so this one might, as well).
    • Provide a mechanism for internal links to work.  Since the new PUI application will currently go directly to a search result page when there is only a single result, this may be as simple as making it possible for the refID elements to be searched exclusively.  See this internal link, as way of example: <ref target="mferd61e965">Family Papers</ref>.  We should be able to search for that @target value and arrive at the following page in the test corpus: /resources/27#tree::archival_object_23565 (since that archival object has that exact ref ID), which is part of the LoC repository. 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-995
    • Add a container-only view of any resource record that has containers attached, which will allow users to “peek” inside each box to see the titles of the contents contained within each (taking advantage of the new top container model); or, barring that feature, look at adding an Excel/CSV export option for that same type of flattened view. 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-838
    • Update the “Collection organization” side panel so that it will include more links beyond just the links to any immediate children (as per the Cherry Hill design; or, at the very least, move that section to the bottom of the page and allow all descendants to show as per the current PUI). 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1483
    • Update the metadata that is embedded in each HTML header to help optimize how search engines understand the ArchivesSpace PUI.  Title, dates, creator information, and repository information should be mapped to JSON-LD. 
      Jira Legacy
      serverJIRA (archivesspace.atlassian.net)
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyAR-1484
    • Merge the new PUI code back into the ASpace core, addressing any other loose ends already identified (e.g. “see more” javascript file).
  • Any requested changes to the testing schedule / procedure?
  • Next meeting / general schedule
    • 3 p.m. EST, January 23rd