You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default marctable outputs a table with 215 columns, one for each MARC field in the Avram schema. So for example the 245 subfield gets serialized to the F245 column. You can override this by using the --rule option to specify specific field and field/subfield combinations if you want.
But I wonder if for some use cases you would actually want to have all Field/Subfield combinations? So like F245A, F245B, F245C, etc. It would make the table quite wide (not sure how wide yet). But perhaps the size wouldn't be greatly impacted. Maybe if not the default it could be an option like:
By default marctable outputs a table with 215 columns, one for each MARC field in the Avram schema. So for example the
245
subfield gets serialized to theF245
column. You can override this by using the--rule
option to specify specific field and field/subfield combinations if you want.But I wonder if for some use cases you would actually want to have all Field/Subfield combinations? So like
F245A
,F245B
,F245C
, etc. It would make the table quite wide (not sure how wide yet). But perhaps the size wouldn't be greatly impacted. Maybe if not the default it could be an option like:The text was updated successfully, but these errors were encountered: