Cool! so where is this Edit Field Data tool will be located?
________________________________________
From: MarcEdit support in technical and instructional matters [[log in to unmask]] On Behalf Of Terry Reese [[log in to unmask]]
Sent: Friday, April 04, 2014 11:45 PM
To: [log in to unmask]
Subject: Re: Edit Field Data
Here’s an example of how you would do recursive replacement of a field, resulting in multiple fields. http://blog.reeset.net/archives/1295
--tr
From: MarcEdit support in technical and instructional matters [mailto:[log in to unmask]] On Behalf Of Veve, Marielle
Sent: Friday, April 4, 2014 1:30 PM
To: [log in to unmask]
Subject: Re: [MARCEDIT-L] Edit Field Data
That would be Awesome Terry, thanks for your work! (e.g. This will allow us to separate a bunch of subject headings if we have them in one field only, the same with other fields)
----------------------------------
Marielle Veve
Metadata Librarian
Thomas G. Carpenter Library
University of North Florida
1 UNF Dr., Jacksonville, FL 32224
[log in to unmask]<mailto:[log in to unmask]> 904-620-5726
From: MarcEdit support in technical and instructional matters [mailto:[log in to unmask]] On Behalf Of Terry Reese
Sent: Friday, April 04, 2014 12:55 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: Edit Field Data
So, you’d have access to everything after the indicators, with a mnemonic to expose the stem of the field/indicators in case your change requires the creation of multiple fields from a specific set of data, allowing you to clone the stem of the field. Essentially, any regular expression you use with the replace function that starts like this: (=500.{4}) – could be used in the field function, without the need to do the first part – which then allows you to consider recursion in an easier way. I’m working on creating a few examples that show some of the ways this might be useful.
I hadn’t considered the add if didn’t exist – I’ll need to take a look at what that would mean and how that might be applied. And in terms of COM, I could see adding it to the process.
--tr
From: MarcEdit support in technical and instructional matters [mailto:[log in to unmask]] On Behalf Of Jim Taylor
Sent: Friday, April 4, 2014 11:37 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [MARCEDIT-L] Edit Field Data
Keeping in mind that my questions are leading to the question/request that this be included as part of the COM set of Methods.
Just to make sure I understand…Will the “Field” be the 650 or 650a? If 650a I assume it would only affect the subfield a? Wasn’t sure when you said “You’d be able to edit all data after $a”. I can see a clear use for both options.
Also, trying to decide if having an option where it would Add the “Replace” data if it isn’t found, would be useful at times. Cases where you were find/replacing on subfield but for some reason it didn’t exist. Guess this logic would center on the tag+subfield rather than the text as hard to imagine you would insert text into other text without a clear idea what was there. Not sure if any of this makes sense. Having the ability to add a tag if it is missing would be useful…sort of like SQL’s “Insert Ignore Into…” logic Maybe a separate Method would make more sense. Something like the Extract method I mentioned before to determine existence and an Insert Method to handle the other.
Sorry if I am taking this thread in the wrong direction. I think the initial questions are relevant though.
Thanks.
Jim
From: MarcEdit support in technical and instructional matters [mailto:[log in to unmask]] On Behalf Of Terry Reese
Sent: Thursday, April 03, 2014 8:21 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Edit Field Data
So, I’m in the process of creating an Edit Field Data function – essentially, this should help folks that aren’t comfortable doing regular expressions, but want to do work against very specific fields. However, for those interested in regular expressions, it should give you more power to edit data in new ways (i.e., recursive data processing). At this point, I’m thinking that this function will allow you to edit the data that starts after the subfield – i.e., in a field like:
=650 \7$a….
You’d be able to edit all data after $a….
The idea here is that if you need to edit groups of fields, or edit indicators, there are other functions for that. At least, that’s kind of what I’m thinking. What I’d like to make certain is if that assumption is correct. Here’s what it looks like right now (below).
--tr
[cid:image001.jpg@01CF505F.F668EB20]
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask]<mailto:[log in to unmask]>. To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]<mailto:[log in to unmask]>.
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask]<mailto:[log in to unmask]>. To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]<mailto:[log in to unmask]>.
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask]<mailto:[log in to unmask]>. To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]<mailto:[log in to unmask]>.
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask]<mailto:[log in to unmask]>. To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]<mailto:[log in to unmask]>.
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask] To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]
________________________________________________________________________
This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit. If you wish to communicate directly with the list owners, write to [log in to unmask] To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]
|
