Feature #10193

Add source-name field to archival record Admin area in edit template

Added by Mike Gale almost 4 years ago. Updated over 2 years ago.

Status:VerifiedStart date:08/10/2016
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Import/Export
Target version:Release 2.4.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

With all our new import update options, the user will need a better view of what source-names previously imported records were set with. To facilitate this, Dan and I discussed that maybe if the user is logged in / viewing an archival record, that in the administrative section of that record we can also display any source-names in the keymap associated with that record.

source-name-ui.png (14.8 KB) Dan Gillean, 08/10/2016 04:34 PM

Screen Shot 2016-11-14 at 1.59.30 PM.png (77.1 KB) Steve Breker, 11/14/2016 05:28 PM

Screen Shot 2016-11-14 at 1.58.24 PM.png (73.1 KB) Steve Breker, 11/14/2016 05:28 PM

History

#1 Updated by Dan Gillean almost 4 years ago

  • File source-name-ui.png added
  • Subject changed from Add source-name field to archival record view template if user logged in to Add source-name field to archival record Admin area in edit template
  • Target version set to Release 2.4.0
  • Requires documentation set to Yes

After looking at the UI, and thinking about maintaining standards compliance, I'm going to suggest we add this to the Administration area of the archival description edit templates, rather than the view page. I've updated the title of this issue to better reflect that.

The only place to put this in the view page template would be the control area - but while we've accidentally deviated from the standards somewhat due to early ICA-AtoM development, this is still generally following the standards, included in import/exports, and I'm hesitant to add an AtoM-specific field here. We could potentially add something to the context menu, but there's a lot going on there already, and one more think to check for visibility before loading adds minor performance degradation over time - this way we avoid that problem, and don't end up awkwardly mixing information types.

I'm attaching a crude wireframe of what I'm thinking. It's less convenient for users to have it in the Admin page (so they have to enter edit mode to see the data), but I can't think of a better place to put it, and i'm hoping that as time goes forward, the need for this on an individual basis is less as workflows change to accommodate the new functionality.

Let me know if you have other questions!

#2 Updated by Dan Gillean almost 4 years ago

  • Target version changed from Release 2.4.0 to Release 2.5.0

#3 Updated by Dan Gillean over 3 years ago

  • Target version changed from Release 2.5.0 to Release 2.4.0

#4 Updated by Steve Breker over 3 years ago

Ready for code review.

https://github.com/artefactual/atom/pull/464

Screen shots attached show Admin area for record with an associated keymap record, and one showing Admin area when there are no assoc keymap records.

#5 Updated by Jesús García Crespo over 3 years ago

  • Status changed from Code Review to In progress
  • Assignee changed from Nick Wilkinson to Steve Breker

LGTM! Thanks for the screenshots!

#6 Updated by Steve Breker over 3 years ago

  • Status changed from In progress to QA/Review
  • Assignee changed from Steve Breker to Nick Wilkinson

Ready for QA.

#7 Updated by Nick Wilkinson over 3 years ago

  • Assignee changed from Nick Wilkinson to Sara Allain

#8 Updated by Sara Allain over 3 years ago

  • Status changed from QA/Review to Deploy
  • Assignee changed from Sara Allain to Nick Wilkinson

Looks good!

Nick, I don't think this falls under the umbrella of all the other CCA/UN import/export work, but setting it to deploy just in case.

#9 Updated by Nick Wilkinson over 3 years ago

  • Status changed from Deploy to QA/Review
  • Assignee deleted (Nick Wilkinson)

#10 Updated by Dan Gillean over 3 years ago

  • Status changed from QA/Review to Verified

Note for docs: when importing via the UI, there's no way to set the source name during import - so by default, AtoM will use the filename of your CSV. Source name appears in the Admin area for files that have been imported - e.g. only visible a) if the file was imported, and b) if you are logged in and viewing the record in edit mode.

#11 Updated by Dan Gillean over 2 years ago

  • Requires documentation deleted (Yes)

Also available in: Atom PDF