-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submissions from CompSci #30
Comments
It is also failing for this submissions:
This submissions were created with: Toppan Merrill Bridge iXBRL 9.6.7713.40453 and not workviva. |
Thank you! |
The issue is that the parser fails when parsing the context because the taxonomy could not be found. The context: <context id="c77_From1Dec2022To31Dec2022_HK_SubsequentEventMember">
<entity>
<identifier scheme="http://www.sec.gov/CIK">0000747540</identifier>
<segment>
<xbrldi:explicitMember dimension="us-gaap:DeferredRevenueArrangementTypeAxis">**pf0:HK**</xbrldi:explicitMember>
<xbrldi:explicitMember dimension="us-gaap:SubsequentEventTypeAxis">us-gaap:SubsequentEventMember</xbrldi:explicitMember>
</segment>
</entity>
<period>
<startDate>2022-12-01</startDate>
<endDate>2022-12-31</endDate>
</period>
</context> The namespace: xmlns:pf0="http://xbrl.sec.gov/country/2020-01-31" In this particular case the schema for the namespace was not defined, but it is a standard taxonomy and should be added to https://github.com/manusimidt/xbrl_parser/blob/34952a6a1185a81d767c591d3a42f53423b558d5/xbrl/taxonomy.py#L160-L188 |
@Pablompg Thank you for the issue! |
Thank you for solving the issue @manusimidt . Would you consider a new release with this issue solved? |
Yes of course, sorry i forgot. |
When trying to parse this submission: https://www.sec.gov/Archives/edgar/data/747540/000121390021011934/sprs-20201130.xml the library failed with the error:
I will have a deeper look at the error but it seems that this submission does not contain an
id
for each fact. Will have to analyse it and see if it can be parsed or not.The text was updated successfully, but these errors were encountered: