<div dir="ltr">Hey,<div>I have been working on the proposal for the adding import/export feature to Grandham. The proposal is mostly done and am looking to submit it.</div><div><br></div><div>I would like to get some feedback from the community whether my approach is right.</div>

<div><br></div><div>I'm mentioning some of my key notes here.</div><div><br></div><div><span><i><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">There are some problems that we will have to solve to implement MARC record import and export.</span></p><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"><br></span></p><p style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">1. Personalized field names, in indic languages</span></p>
<div style="font-family:arial,sans-serif;font-size:13px;font-style:normal">Ability for Grandham user to create his MARC-21 reference for use in the software.</div><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"></span></p><div style="font-family:arial,sans-serif;font-size:13px;font-style:normal">Eg. 100 $a(field, subfield) in MARC-21 refers to name, we keep some default value in database 'Name' while giving the flexibility for the user to call this name, personal name or any localized format (integration using i18n, not sure on this though), similarly for every thing other fields. </div>
<div><br></div><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><i style="line-height:normal"></i><br></p><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt;display:inline!important">
<span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">2. Migrating to MARC21:</span></p>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">Currently Grandham has a system to process bibliographical information. Implementing MARC21 would mean migrating the current system architecture to enable to use and process MARC21 data efficiently. This project should make some workaround to migrate the current cataloging structure to use MARC21 data structure in the database completely.</span></p>

<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">As there is a live version of Grandham with a lot of records running, feature must be added to compile the existing records into MARC format database to enable the use of existing records as MARC.</span></p>

<br><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">3. MARC records</span></p><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">MARC21 has a lot of records that will mostly go unused, this means that we will have to allow the flexibility for the admins to opt out from using particular fields.</span></p>

<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">Too many fields also means that we have to restrict the number of fields displayed in the view according to user.</span></p>

<br><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"></span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">4. Export data to MARC21</span></p>

<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">Once we completely migrate Grandham to use MARC21 inherently exporting can be easily handled. Export formats will include MARC21 and MARCXML</span></p>

<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">Exporting to MARC can also be done based on criteria.</span></p>

<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">1. Export all Grandham records.</span></p>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">2. Export records that belong to a particular library.</span></p>

<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">3. Export record based on publisher.</span></p>

<br><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"></span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">4. Import MARC21</span></p>

<span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">The import function can be handled to import MARC bibliographical data completely. The user can decide later as to what data can be displayed.</span></i></span><br>

</div><div><span><i><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"><br></span></i></span></div><div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">I've had discussion with mentor Ershad, attached the discussion. Some key discussion areas to note here are.</span></span></div>

<div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"><br></span></span></div><div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">1. It was decided upon discussions to import every field from MARC21, any points as to why not?</span></span></div>

<div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">2. Will there be any particular need to use MARCXML, I don't see any major benefits. Probably there should be something.</span></span></div>
<div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">3. Will there be a need to opt out from exporting a field?</span></span></div><div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial"><br>
</span></span></div><div><span><span style="vertical-align:baseline;white-space:pre-wrap;background-color:transparent;font-family:Arial">Thanks.</span></span></div></div>