QuickMARC: 2020-02-28 FOLIO Implementation Group Meeting Notes

Naming the tool

 @Stephanie Buck

Thinking about a name for this - SMRE won't really work in FOLIO.  

fastMARC vs quickMARC - think about these two for the week and then decide next week

miniMarc?

• there is already an OCLC controlled vocab called fast, so that has been eliminated.

• We went with quickMARC!

Keyboard shortcuts

Everyone

What keyboard shortcuts are needed in this tool at launch; what can be added to a list for later?

Cut, copy, paste, save, page up, page down, tab from field to field, 

• Discussion around adding new fields and related steps

• There is a way to add a new row, but might not be accomplished via shortcut

Delimiter

  @Stephanie Buck indicated that the $ sign will be used - and then there was a discussion about using the proper delimiter as specified by UTF-8.  Good to be consistent with other marc-like apps - which appears to be the $

Also want a space after - but then saved without (as is standard marc practice)

Controlling fields

@Stephanie Buck

Verifying which fields can and can't be edited, deleted and moved within a record

• 001 and 999 fields should not be editable - incorrect entry would disallow them to be entered into the SRS

• FOLIO uses the 999 $ff - this has to be locked down. (Ann-Marie)

• Also 245 $a  

• All the above are mandatory.  Can't be deleted, and can't be empty. 

• Maybe use the OCLC design as a prototype. 

• OCLC - would be useful for Stephanie to have screen shots

• @Andrew Clark @Raegan Wiechert  to supply 

• Discussion of editing the 008 - would we be doing it via quickMARC?  Dropdowns would be difficult, but helping user to know what byte they are.  Maybe have the system parse the fields.  

Reordering fields

@Stephanie Buck

Drag and drop vs arrows

• Requests has drag and drop (tried a demo but it didn't work)

• Arrows may be more precise?

• There will not be automatic ordering - which is preferred

• Whatever is easier and dependable

• Here's the Request-related drag-and-drop stories from Jira - via @Ann-Marie Breaux (Deactivated)
  https://folio-org.atlassian.net/browse/UIREQ-112
  https://folio-org.atlassian.net/browse/UIREQ-314

SRS messages - system initiated error

If for some reason the record can not be saved from the system perspective there should be the standard error message that indicates it's the system's fault, verses the user's fault. (user initiated errors)

@Ann-Marie Breaux (Deactivated)  to find that 

User messages - use initiated error

Limited to errors that would break SRS (see above) 

Permissions

Discussed options and completing the spreadsheet