-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
We had choosen a prefix of “marcxml” as the data format was marcxml, not
MARC21 (which really is the combo of USMARC and CANMARC). However,
http://www.openarchives.org/OAI/2.0/guidelines-marcxm…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
This is related to Issues 275 that I posted recently. I found a document that
specifies that the prefix "marc21" be used for this schema:
http://www.openarchives.org/OAI/2.0/guidelines-marcxml…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…
-
```
Many of the importer options panels have a field to specify a line terminator
other than the default \n, but, as far as I can tell, no importer actually
implements that option.
We should either…