Thanks Elizabeth, would it be possible to get a copy of that script? I have a few scripts for editing MARC data but I would like to see how others have done it. Josh
On Thu, Jan 15, 2026 at 8:57 AM Thomsen, Elizabeth <[email protected]> wrote: > We have a script that runs daily and finds new 263 fields with any of > these formats: > 4 digit dates MMYY > 6 digit dates YYYYMM > 8 digit dates YYYYMMDD > > It reformats them to MM/DD/YYYY and removes the 263 from records if the > date is in the past. I'm attaching a screenshot from our catalog but we're > now using Aspen for our public catalog, without this data. > > > On Thu, Jan 15, 2026 at 9:38 AM Josh Stompro via Evergreen-general < > [email protected]> wrote: > >> A custom facet might be the way to go, thanks for the suggestion. That >> would make it much more accessible to users. We would probably purge the >> info after a certain amount of time, I'm not sure we need to be able to >> show what was released several months / years ago for each month. >> >> Josh >> >> >> >> On Thu, Jan 15, 2026 at 8:23 AM Sierra Chastain-Rittue via >> Evergreen-general <[email protected]> wrote: >> >>> Hi, >>> >>> I am fully spit-balling with this, but you may be able to make a custom >>> facet >>> <https://aspen-discovery.atlassian.net/wiki/spaces/Help/pages/381648900/Facets#Custom-Facets> >>> that looks at that field in the MARC? That could get messy quickly, though, >>> with variations in date format and changes to pub dates. A translation map >>> that you maintain regularly may be necessary, in that case. I'll be curious >>> to see if you can get this working somehow! >>> >>> Best, >>> Sierra >>> >>> On Thu, Jan 15, 2026 at 9:06 AM Karen Young via Evergreen-general < >>> [email protected]> wrote: >>> >>>> Hi Josh -- I don't think that I have all the pieces of the puzzle, but >>>> I might have a few. We have pub date information come over in our vendor >>>> brief records in the 260 $c. For us and our import settings, if the >>>> incoming record matches to an incumbent record, that pub date is NOT >>>> retained in the MARC, but I suspect there could be a way to retain it by >>>> editing your import settings (maybe? I've never actually attempted this.) >>>> Ingram allows you to format the pub date in several ways (and you can also >>>> have it come over in the 246 $c): >>>> [image: image.png] >>>> I've worked with vendors other than Ingram to include pub dates in our >>>> MARC downloads and they've all been able to do it. >>>> >>>> As for how you could easily find and use info from the 260 $c or 264 $c >>>> in Aspen... I'm not sure. (Maybe there's a way to get the date out of the >>>> MARC and into a notes field or call number in an automated fashion?) Of >>>> course the dates do occasionally become incorrect if pub dates get pushed. >>>> >>>> Hope some of this is helpful. >>>> >>>> Best, >>>> Karen >>>> >>>> *Karen Young* *(she, her, hers)* >>>> Manager of Cataloging & Acquisitions >>>> Kirkwood Public Library <https://kirkwoodpubliclibrary.org/> >>>> >>>> >>>> On Wed, Jan 14, 2026 at 4:35 PM Josh Stompro via Evergreen-general < >>>> [email protected]> wrote: >>>> >>>>> Hello, I was recently asked about generating lists of titles in Aspen >>>>> that will be released by month for 2026. We use on order records to get >>>>> those titles into our system so customers can start placing holds on them. >>>>> >>>>> Does anyone have a system for pulling in the release dates right now? >>>>> Anyone make use of the release dates for marketing? >>>>> >>>>> We have some records with MARC 263a data that was already added, but >>>>> only 38% of our on order records come in with that data. And it looks >>>>> like >>>>> the data that is there isn't following the standard of YYYYMM and is >>>>> mostly >>>>> YYMM. With a few records having YYYYMMDD info. So it needs to be cleaned >>>>> up in any case. >>>>> https://www.loc.gov/marc/bibliographic/bd263.html >>>>> >>>>> It looks like a keyword search in aspen will pull up records based on >>>>> the 263a data - 2601 or 202601 works to grab those records. >>>>> >>>>> So I was just looking around at how I could pull in that data for the >>>>> rest of them without making extra work for our cataloger. >>>>> >>>>> It looks like amazon probably has the information in their APIs. I >>>>> checked a few titles in Google Books API and didn't get any results, and >>>>> tried Open Library also, but they don't seem to have unreleased books in >>>>> my >>>>> spot checks. I don't have an ISBNdb account to see if they include the >>>>> street date. >>>>> >>>>> Thanks >>>>> Josh >>>>> [image: Company logo] >>>>> *Josh Stompro* >>>>> *IT Director * >>>>> [email protected] | 218-233-3757 ext. 139 >>>>> *Lake Agassiz Regional Library* >>>>> 118 5th ST S >>>>> Moorhead MN 56560 >>>>> www.larl.org >>>>> *Our mission is to enrich lives and strengthen communities.* >>>>> _______________________________________________ >>>>> Evergreen-general mailing list -- >>>>> [email protected] >>>>> To unsubscribe send an email to >>>>> [email protected] >>>>> >>>> _______________________________________________ >>>> Evergreen-general mailing list -- >>>> [email protected] >>>> To unsubscribe send an email to >>>> [email protected] >>>> >>> >>> >>> -- >>> >>> Sierra Chastain-Rittue (she/they) >>> Web Support Specialist, C/W MARS, Inc. >>> >>> ------------------------------ >>> >>> [image: icon] [email protected] | [image: icon] www.cwmars.org >>> >>> [image: icon] 508-755-3323 x 1 >>> _______________________________________________ >>> Evergreen-general mailing list -- >>> [email protected] >>> To unsubscribe send an email to >>> [email protected] >>> >> _______________________________________________ >> Evergreen-general mailing list -- >> [email protected] >> To unsubscribe send an email to >> [email protected] >> > > > -- > Elizabeth B. Thomsen > (she/her) > Member Services Manager > NOBLE: North of Boston Library Exchange > Danvers, Mass. > >
_______________________________________________ Evergreen-general mailing list -- [email protected] To unsubscribe send an email to [email protected]
