Excel compatibility

32 views
Skip to first unread message

Friedman, Jason

unread,
Apr 28, 2025, 11:57:09 AMApr 28
to openalex-...@googlegroups.com

Hi All,

 

Would anyone be able to provide guidance as to how "Shorten column values for Excel compatibility" is supposed to work when exporting results to CSV? I still seem to get exports with too much data in cells. For example, this authors.institutions field for this work exceeds the 32,767 character limit in Excel: OpenAlex | The evolution of SARS-CoV-2 seroprevalence in Canada: a time-series study, 2020–2023.

 

Thank you!

 

-Jason

 

Jason Friedman, BA, MA, MIS
he/him

Assistant Dean, Collections and Discovery

 

University of Saskatchewan

University Library

Ph: (306) 966-8114

 

I acknowledge that I live and work on Treaty 6 Territory and the Homeland of the Métis. We pay our respect to the First Nations and Métis ancestors of this place and reaffirm our relationship with one another.

 

Kyle Demes

unread,
Apr 28, 2025, 1:40:01 PMApr 28
to Friedman, Jason, openalex-...@googlegroups.com
Hi Jason (et al),
It shortens cells to 30k characters, below excel's limit. When I export the record for that work, it opens successfully. I'm wondering if you're converting or using another encoding when opening in excel that might be adding more characters to the cell? Mine is UTF-8 and works fine.

Try opening excel, then under the "Data" tab, click 'get data from text/csv' and manually choose the file to see if that works. If so, you might want to change the default encoding you open csv files with or just get data manually once in excel for these files.

Let me know though if there is another issue,
kyle

--
You received this message because you are subscribed to the Google Groups "OpenAlex Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openalex-commun...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/openalex-community/YT1PR01MB4696822D8697F8933BD77B7DE0812%40YT1PR01MB4696.CANPRD01.PROD.OUTLOOK.COM.

Friedman, Jason

unread,
Apr 28, 2025, 3:47:15 PMApr 28
to Kyle Demes, openalex-...@googlegroups.com

Hi Kyle,

 

That seems to have worked! I wouldn’t have thought encoding would be the issue, but looks like it. My new issue seems to be embedded new line characters (\n) (see for example: api.openalex.org/works/W4353070816). But I’m sure I’ll sort it out (though let me know if you have an easy method).

 

Thanks!

 

-Jason

 

Jason Friedman, BA, MA, MIS
he/him

Assistant Dean, Collections and Discovery

 

University of Saskatchewan

University Library

Ph: (306) 966-8114

 

I acknowledge that I live and work on Treaty 6 Territory and the Homeland of the Métis. We pay our respect to the First Nations and Métis ancestors of this place and reaffirm our relationship with one another.

 

From: Kyle Demes <ky...@ourresearch.org>
Sent: Monday, April 28, 2025 11:40 AM
To: Friedman, Jason <jason.f...@usask.ca>
Cc: openalex-...@googlegroups.com
Subject: Re: [openalex-community-group] Excel compatibility

 

CAUTION: External to USask. Verify sender and use caution with links and attachments. Forward suspicious emails to phis...@usask.ca

Reply all
Reply to author
Forward
0 new messages